-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is not possible to rename a branch if only the casing of letters changes #2169
Comments
No, it's not possible to do this because of the case-insensitive file system restrictions.
It's not possible even in the command line:
|
@DanPristupov thank you and thanks for the explanation, now I understand. And sorry, I tried just the first approach ( Anyway, in such a case, I'd consider adding a warning message to the "Rename Local Branch" dialog to prevent future bug reports -- when the entered "New name" differs only in letter casing, show something like: |
Well, recognizing if file system is case-insensitive is not as easy as it sounds :). Even on mac there are many of them (APFS, HFS+ can be both case sensitive and not), NTFS, exFAT, FAT32, network drives and macFUSE. I guess there is a reason why git itself doesn't show a more helpful message. P.S. Since we are here. This limitation is solved in the new reference format in git 2.45 (this format is not supported by Fork yet): https://about.gitlab.com/blog/2024/04/30/whats-new-in-git-2-45-0/#reftables-a-new-backend-for-storing-references |
Version 2.44.3
Steps to replicate:
foo
(As a workaround I have to rename
foo
tofoo2
and then toFoo
... or use git commands for renaming)The text was updated successfully, but these errors were encountered: