5 ms·
I feel like this will break a very significant amount of tooling
by VWWHFSfQ 6y ago
I feel like this will break a very significant amount of tooling
- akerro 6y agoNow that consider all tools need to support new non-offensive terminology and old racist terminology used in existing projects
- VWWHFSfQ 6y agoI'm saying that every tool/service that integrates with Github will now have to know whether the "default" branch is called master or main. Bugs will be caused by that and a lot of services will break.
- herbstein 6y agoThey already had to know that. Plenty of repos use `develop` as their primary branch name.
- exogen 6y agoThen that tooling was broken to begin with.
- VWWHFSfQ 6y agoNewsflash: most software makes assumptions that it shouldn't. Doesn't mean it's acceptable for something like Github to break it just because "well, you shouldn't have done that".
- there_the_and 6y agoYes. Software evolves as the environment evolves. Software that can't evolve gets replaced.
- sebazzz 6y agoWhy? You were always free to delete or rename the master branch. There are enough repositories which don't have a master branch. Unlike SVN (trunk), in git "master" really has no value to the VCS. I also assume this will be for new repositories, so Github won't break builds by changing existing repositories - because that would indeed mess up a lot.