1
I created a repository on Github and sent my application containing an X folder with the full name in lower case, when actually the first letter of the name should be uppercase.
To solve this problem, I executed the following command:
git config core.ignorecase false
I managed to change the name of the folder and gave push
to the repository. The problem is that in Github, the folder with the lowercase name is still there, along with the uppercase folder. Example:
folder/
Folder/
file.txt
When I give one pull
or clone
to remove the lower case folder, Git generates the following warning:
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
And when I open the directory of my application, with the files and folders pulled from Github, here on the computer, only appears the folder with the name in upper case, preventing me to delete the folder with the lower name.
Folder/
file.txt
What do I do to delete the folder with the old name?
Related: How to make Git case sensitive?
– Luiz Felipe
The problem is because by default Git is not case sensitive. Once the sensitivity is activated (as you yourself put it at the beginning of the question), the problem would not occur in the first place. Of course, this doesn’t solve the problem that has already occurred, but if Git were always box-sensitive it wouldn’t happen, so it serves as "prevention" for similar future problems. That’s why I posted the comment.
– Luiz Felipe