Hi @bistritapcv,

This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information.

As you’ll notice, your Topic is now in the How to use Git and GitHub board. No action is needed on your part; you can continue the conversation as normal here.

Let me know if you have any other questions or if I can help with anything else.

Cheers!

Unfortunately, no one has answered.

how to get it enabled after its installed

I would just reinstall gitbash, quick and easy!

Hm, I have symlinks=true, but ln -s largeFolder shortcut just starts to make full copy… 

$ cat /c/ProgramData/Git/config
[core]
symlinks = true
$ echo Orig > 1

$ ln -s 1 2

$ cat 2

Orig

$ echo Modified > 2

$ head 1 2

==> 1 <==

Orig

==> 2 <==

Modified

This answer worked for me:
https://stackoverflow.com/a/40914277/3990615

That did it!

1. run as admin

2. export MSYS=winsymlinks:nativestrict

If you enable “Developer mode” in the Windows 10 settings you don’t have to run the shell as Admin.

That is, run Git Bash as admin, run the command export MSYS=winsymlinks:nativestrict, then run ln -s oldFile newLink to your hearts content within that session.

I can confirm ln symbolic link behavior is determined by the MSYS environment variable, more info the Cygwin docs.

You don’t need to be admin, just configure the User Rights Assignment

Before clone the repository you can set the config:

git config --global core.symlinks true

If you add the MSYS variable to your system's environment variables, you won't have to run export MSYS... every time.

See Setting the path and variables in Windows

Variable name = MSYS
Variable value = winsymlinks:nativestrict

Now every time you open your bash shell, the setting will be there.

Jesus. Took me like 30 minutes to figure out the inconsistencies I was facing was because ln -s created a copy instead of a symlink. Very strange default behaviour.