Yes like companies who have thousands of repos with master as the main branch. It really wouldn’t make sense to switch halfway and be working on different repos with different primary branches.
Not the biggest hurdle to overcome but also… Why should you have to?
Do you really have to, tho? One can keep using masters, move them to mains, or even symlink one to another so that everyone is comfortable with whatever they’re used to. Seems like a non-issue to me 🤷
We’ve ended up with a 50:50 chance of what any repo is doing. All depends on when the repo was created (old ones are all master) and if the creator tried to preserve consistency or not (yes: master, no: took the default of main).
It’s an issue, because many tools default to a certain branch, and people do too. So each build pipeline has to be changed, each dev has to check for each repo he’s working on, whether it’s using main or master, etc, etc.
Just think about what hell would break loose, if Microsoft would be forced to rename C: to something else because someone was reminded of the "C word ".
For a while, yes, you had to. Every new repo would be main while old ones remained master. Tools that default to a specific branch aside now you had to remember and check which branch you are merging into every time.
Yes like companies who have thousands of repos with master as the main branch. It really wouldn’t make sense to switch halfway and be working on different repos with different primary branches.
Not the biggest hurdle to overcome but also… Why should you have to?
Do you really have to, tho? One can keep using
master
s, move them tomain
s, or even symlink one to another so that everyone is comfortable with whatever they’re used to. Seems like a non-issue to me 🤷We’ve ended up with a 50:50 chance of what any repo is doing. All depends on when the repo was created (old ones are all master) and if the creator tried to preserve consistency or not (yes: master, no: took the default of main).
It’s annoying and pointless.
Symlink a git tag?
I mean smth like
git symbolic-ref refs/heads/master refs/heads/main
. Not sure if it’s a bad practice or smth, thoIt’s an issue, because many tools default to a certain branch, and people do too. So each build pipeline has to be changed, each dev has to check for each repo he’s working on, whether it’s using main or master, etc, etc.
Just think about what hell would break loose, if Microsoft would be forced to rename C: to something else because someone was reminded of the "C word ".
For a while, yes, you had to. Every new repo would be
main
while old ones remainedmaster
. Tools that default to a specific branch aside now you had to remember and check which branch you are merging into every time.