From: Simon Thurston <simongethurston@gmail.com>
To: git@vger.kernel.org
Subject: [Bug Report] git config includeIf not traversing symlink subdirectories
Date: Fri, 3 May 2024 17:31:59 -0400 [thread overview]
Message-ID: <CAKx51amU_c9EU+573RWDc0+w3V2u5TSk+mQhts1gYyKRhxGCzQ@mail.gmail.com> (raw)
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]
next reply other threads:[~2024-05-03 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 21:31 Simon Thurston [this message]
2024-05-03 23:06 ` [Bug Report] git config includeIf not traversing symlink subdirectories brian m. carlson
[not found] ` <B240544D-1695-4627-B7EC-5C9CA7716265@gmail.com>
2024-05-04 1:06 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKx51amU_c9EU+573RWDc0+w3V2u5TSk+mQhts1gYyKRhxGCzQ@mail.gmail.com \
--to=simongethurston@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).