Getting "Changes not staged for commit" after cloning project about sublime-gitignore HOT 2 CLOSED

This is happening because there are files with the "same" name differing only by case in the repository. On case-insensitive filesystems like APFS/HFS (by default) and NTFS, that means files like "nanoc.gitignore" and "Nanoc.gitignore" collide during checkout and one overwrites the other.

For users on case-insensitive filesystems, there is no fix or workaround. (Please note: Git's core.ignorecase is not a workaround for case-insensitive filesystems. It's a setting which allows Git to function on such filesystems. The documentation was recently updated to reflect this more clearly.)

The best "fix" for users is to eliminate the duplicates--choose one case and use it, and remove the file with the other case from the repository.

from sublime-gitignore.

@bturner I thought about line-ending but didn't check the file names. 🙄
Thank you so much!

from sublime-gitignore.