> On 2025-04-02 at 22:41:50, brian m. carlson wrote: > > What is your particular use case that requires changing this value? Hi, thank you for your reply. Just recently started working with symlinks in git and I've found that in Git for Windows they are disabled by default (https://gitforwindows.org/symbolic-links.html). It's possible to just change the setting in system config or override it in global config, but it's probably safe to assume that the average Windows user will have them disabled. And if your repo needs them, it's probably more reasonable to ask the user to enable symlinks in a local config, not global. So, you can enable them during clone `git clone -c core.symlinks=true` but I guess as a user (and symlinks not being used very often) you typically learn about repo having symlinks and you needing them after repo was cloned. So this is the use case I've found for `git checkout` or some other command refreshing files based on current `core.symlinks` value. Without this feature you would need to have a script where you list all symlinks, remove them with `rm` / `del` and only then you can check them out. Maybe there are similar cases but on Unix when users would want `core.symlinks` disabled globally and be enabled on a per-repo basis but I can't imagine why.
