Thank you for filling out a Git bug report! Please answer the following questions to help us understand your issue. What did you do before the bug happened? (Steps to reproduce your issue) On Windows. Create a directory. Configre a gitconfig file to includeIf gitdir that directory. Add any configuration you wish to the gitconfig file pointed to by the includeif path. Inside the created directory, create a symlink to a UNC Path/Network location. Change directory into the symlinked directory. Run git config --show-origin on a configured value. What did you expect to happen? (Expected behavior) The value configured in the includeIf path to be found. What happened instead? (Actual behavior) No configuration data found. What's different between what you expected and what actually happened? Git seems to be unable to traverse subdirectories that are symlinks to include any git repositories stored inside them. Anything else you want to add: I am well aware that while running Windows 11 in a corporate environment there is likely something silly that is stopping me from doing something correctly within our Group Policy. However, I just wanted to open a report in case that something is not working. The workaround I had to do for this is to regular include the config file I had written, which is not ideal, even though I am pretty sure that the includeIfs I have after it should override it. I am interacting with git through pwsh 7.4.2. Please review the rest of the bug report below. You can delete any lines you don't wish to share. [System Info] git version: git version 2.45.0.windows.1 cpu: x86_64 built from commit: b5d0511969ccd9ab86395c37e5a7619d8b4e7c32 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 22635 compiler info: gnuc: 13.2 libc info: no libc information available $SHELL (typically, interactive shell): <unset> [Enabled Hooks]
