Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
In version 2.13.0,
If I then open a new shell using version 2.12.2,
This does not appear to be an issue when not in a worktree:
I expected that
It turns out that this is something that affects all case-insensitive filesystems, and isn't specific to this project. See the git mailing list discussion here:
Best practice is to not use
To make it (maybe more) clear: the current implementation of Git (and GfW, too) uses physical files located in the "Git data directory" (typically it's the ".git" folder located in every non-bare repository) to represent most¹ "refs" — which are tags and branches.
This interacts badly with case-insensitive filesystems
¹ The refs which are not used for some amount of time may eventually transition to the so-called "pack files" due to bookkeeping procedures. In this state, they are no longer represented as regular files.