[acdha]

What kind of issues have you encountered? Since NTFS, HFS+, and APFS are all case-preserving the only thing I've ever run into was a Unix-only project where they files which differed only in case (i.e. Makefile and makefile) and the project team fixed that by recognizing that it was just asking for trouble.

[Merad]

I make a branch named 'feature/ABC-123', do some work, and push to the server. You want to take over my branch so you do a fetch then run the command 'git checkout feature/abc-123'. You will check out my branch, but when you go to push back to the server you're going to be push a new branch with a lower case file name unless you realize what has happened and know that you need to run 'git push origin feature/abc-123:feature/ABC-123' to push your changes to the existing remote branch.

[amarraja]

Yep exactly this. We've gotten into messes before when people are working on - or think they are - the same branch. Some os think they are the same, others different.

Also just finished migrating something that ran on IIS to linux, and got the casing pains once again.

If the universe were to be reinvented, I ask please make everything case sensitive by default

[acdha]

Interesting — I've never hit that, presumably because it always works the right way if you use tab-completion or are copying a command from the GitHub/GitLab UI. That's good to know about.

[Merad]

Yeah, it’s not exactly a common problem. I’ve only seen it come up in that scenario when two people with different casing habits try to share a branch.