• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle













  • This, sooo much this! People don’t realize that this change created a lot of unnecessary work to a lot of developers for no other reason than PR or to act smug about it. They solved slavery problem by renaming master to main equally well as they solved homophobia and transphobia by allowing people to specify pronouns on their profiles. Who the hell cares if you identify as tree sap. However many do care if your code sucks or doesn’t follow coding style.





  • Had to refresh my memory, it’s been a while. They didn’t change branch on existing projects, but they did change it on new repos to main by default. Our tools indeed created repositories and configured everything for the developer automatically. However GitHub’s policy meant that you had to either change the tools to detect whether they are working with old repo or new, or go to every new project after automatic configuration fails, configure default branch and then rerun the tool. Same thing then happened to few of our tools that were used for CI.

    All in all they made more work for us for no reason other than be smug about it and it changed exactly nothing.


  • They forced the change. If I wanted otherwise, I had to go and specify per project that master was the default branch, and there were many of those. And whole “insanely fragile” is just nonsense or are you trying to tell me people have conditions and scripts that detects what’s the default branch and use that instead of assuming default name that hasn’t changed for 15 years would remain default?

    Whether you like Linus or not, whatever is released to users stops being a bug and becomes a feature. Not breaking user-space is a must. Instead they achieved nothing and caused a lot of unnecessary work to a lot of developers.