4 ms·
Sure, it’s fine and easy if you’re starting a project today. But if you have any build or deployment automation that interacts with git repos for existing proje
by throwaheyy 6y ago
Sure, it’s fine and easy if you’re starting a project today. But if you have any build or deployment automation that interacts with git repos for existing projects it will be broken by the change.
- iamflimflam1 6y agoThat doesn't really make sense? If you have existing git repos they will still have a branch called master. GitHub did not go into existing repositories and change the names of existing branches.
- enriquto 6y agoBut they did not rename any existing repositories (that would be in very bad taste!). Such an automatic renaming would possibly break a lot of scripts, but this is not what is happening. All old repositories still have their branch names intact. The new repositories can have whatever name you choose. What does "the change" actually do? Is it just in the "new repository" instructions or is there some automated process that may fail? Maybe I'm missing a way to create github repositories besides the "New" button on your user page?
- detaro 6y agoExisting projects are impacted by a changed default for new repositories how?