In Windows 10, Git 2.34, and TortoiseGit 2.13, after the directory is renamed (the lowercase letter is changed to upper case), there is no change analysis when submitting

1. In Windows 10, Git 2.34, and TortoiseGit 2.13, after the directory is renamed (the lowercase letters are changed to uppercase letters), there is no change when submitting. as shown in Figure 1

Figure 1

2. Manually rename it to small letters first, enter the directory after renaming, right-click – change the name, and then modify it to uppercase. Error: Failed to rename, should I try again? as shown in Figure 2

Figure 2

3. Check the valid configuration of TortoiseGit, ignoreCase, ignore the case as true. as shown in Figure 3

Figure 3

core.ignorecase=true

4. Execute the command in the root directory of the current warehouse, set to false. as shown in Figure 4

Figure 4

PS E:\wwwroot\object> git config core.ignorecase false
PS E:\wwwroot\object>

5. Check the valid configuration of TortoiseGit again, ignoreCase, ignore the case as false. as shown in Figure 5

Figure 5

6. Submit again, after the directory is renamed (the lowercase letters are changed to uppercase letters), there are changes when submitting. However, it has changed to a new file, not renamed the file, which is not as expected. as shown in Figure 6

Figure 6

7. Decide to submit a push for this, and then view the changes on GitLab. There are 2 directories. as shown in Figure 7

Figure 7

8. After pulling the code, the local repository still has only one uppercase directory.

9. Execute the command: git config core.ignorecase true, first restore the settings. Reset to the previous version.

10. Re-submit, overwrite the push. as shown in Figure 8

8

11. In the end, it is decided to delete the directory (lowercase) first, and then add the directory (uppercase) to realize the directory rename. Viewing changes on GitLab, there are only uppercase directories, in line with expectations. as shown in Figure 9

Figure 9