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) $ mkdir abc
$ echo "">abc/.keep
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
abc/$ mv abc Abc
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
Abc/ # rename
to Abc/ successfully$ git commit -m "commit Abc/" # commit
$ mv Abc abc
$ git status On branch master nothing to commit, working tree clean # cannot rename again
$ git diff
>""
$ git add .
$ git commit -m "Cannot rename from Abc/ to abc/" On branch master nothing to commit, working tree clean # cannot commit to right, keep old file name / folder name
What did you expect to happen? (Expected behavior) It should be correct to new name although just change upper/lower case, because other commiter can pull it from repo or improve reading clarity.
What happened instead? (Actual behavior) can commit file/folder but cannot fix upper/lower case.
What's different between what you expected and what actually happened? git unable to faithfully represent file/folder upper/lower case changes.
Anything else you want to add:
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.40.0.windows.1 cpu: x86_64 built from commit: 1d90ca2906dd4b7ddaf0669a13c173ec579d794a sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19045 compiler info: gnuc: 12.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
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) $ mkdir abc
$ echo "">abc/.keep
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
abc/$ mv abc Abc
$ git status
On branch master
Untracked files:
(use "git add <file>..." to include in what will be committed)
Abc/ # rename to Abc/ successfully$ git commit -m "commit Abc/" # commit
$ mv Abc abc
$ git status On branch master nothing to commit, working tree clean # cannot rename again
$ git diff
>""
$ git add .
$ git commit -m "Cannot rename from Abc/ to abc/" On branch master nothing to commit, working tree clean # cannot commit to right, keep old file name / folder name
What did you expect to happen? (Expected behavior) It should be correct to new name although just change upper/lower case, because other commiter can pull it from repo or improve reading clarity.
What happened instead? (Actual behavior) can commit file/folder but cannot fix upper/lower case.
What's different between what you expected and what actually happened? git unable to faithfully represent file/folder upper/lower case changes.
Anything else you want to add:
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.40.0.windows.1 cpu: x86_64 built from commit: 1d90ca2906dd4b7ddaf0669a13c173ec579d794a sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 19045 compiler info: gnuc: 12.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
