Microsoft apparently still doesn't quite understand the concept of case-sensitivity in filenames & URLs and just changed to, in turn breaking a ton of canonical URLs and references.

It's incredible how shortsighted and oblivious a company of that size can be, really 🙄

@fribbledom so many times I've had to fix case-sensitivity at work by checking out into linux, recommitting & telling everyone "delete that file & pull, trust me on this"

@FNB_Japan @fribbledom that's what I'm trying to figure out. I thought maybe it was branding, but I can't find any evidence for that

@fribbledom Why am I not surprised? They've been breaking links on MSDN for years. I guess it's only right that they try it with Github, too.

@fribbledom And there you have it, Microsoft strategy in a nutshell.
New tech not ours?::
Embrace, Extend, Take as our own. Damage it so no one else can use it.

@fribbledom ehh no? GitHub redirects any name change. and ignores any casing in the URL:


That's great for GitHub, but it still breaks build systems, imports, caches, image links and other references, because they are now pointing to a different canonical name.


Some of their own repositories use external services, like TravisCI, which now have broken links & references.

Try to click the build badge on and see where it takes you.

@fribbledom blaming Microsoft for a feature in GitHub that other platforms didn't implement or foresee is not the way to go


I'm not sure breaking W3C's standards and various RFCs (3986 as one example) is something I'd call a feature.

Besides that, it's ignoring the case-sensitivity handling git itself imposes, the very tool it builds upon. Keep calling it what you want, it leads to real-world problems and that's what I call a bug.

@fribbledom you can change your username or repository name in GitHub, changing from capital M to lowercase m is a name change. this is supposed to be expected by all platforms using GitHub. all current checked out git repos will stay working. only thing "broken" is cache and apparently Travis who ignored a feature of GitHub.

@eater @fribbledom Github exists in the real world where real people use it, not some fantasy-land where all software doesn’t have bugs or quirks. This is a change that breaks stuff, and they should reverse it, announce it and then do it later if they really need to change it (I don’t see why other for weird esthetic reasons).

@fribbledom @eater but the trailer for the terminal looked good. That's all that matters

@fribbledom I love how quickly celebration turns into "we just broke a lot of things" in that thread.

@fribbledom it seems to me that a lot of tools that use git don't follow redirects.

@fribbledom to be fair ( Microsoft never really got on board with case sensitivity.

@fribbledom Reading through the back-and-forth involving the original committer, it seems clear they knew this would make a mess but chose to proceed anyway.

Odd decision. 🤔

Was it because #Windows filesystems are case insensitive and someone from #Microsoft thought #GitHub runs not on Linux? 🤣


That's part of the problem, as it still changes the canonical name of everything within that namespace: build systems, caches, image references and a bunch of other things will break - as they treat URLs case-sensitively as various RFCs and the W3C suggest.

I guess Microsoft is just learning that lesson now.

@fribbledom I guess I'm just confused why that will happen, since it's not a re-writing case insensitivity. Like, an example of an actual situation where this would cause a problem.

I see why it's potentially an issue but I'm having trouble wrapping my head around the actual impact.


Just a few examples:

Many projects link their GitHub namespace with other services like CIs, Linters, Test Badges, Doc Generators and so on. They usually treat URLs case-sensitively, which now leads to broken references. Try to click the build badge on one of their own projects, and see where it takes you:

Some build systems will fail as they check out dependencies including the full canonical namespace, and now can't find the uppercase version in the filesystem.

@fribbledom Ah, thanks–got it now 👍 sorry to bother you


No need to apologize, I never feel bothered to respond to sensible, intelligent questions!

It also clearly isn't super obvious this would lead to issues, which is why Microsoft probably ended up in this situation to begin with.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!