So creating a new repo on GitHub, you get a set of getting started steps. They changed the default branchname to “main” from “master” due to its connotations with slavery.
When I create a new repo now, the initial getting started steps recommend creating a branch named “master” as opposed to “main” as it was a while ago.
It’s especially weird since the line git branch -M master is completely unnecessary, since git init still sets you up with a “master” branch.
Disclaimer: I have a bunch of private repos, and my default branchnames are pretty much all “master”.
Is this a recent change?
Edit: Mystery solved, my default branchname is “master”. Thanks [email protected] !
God I wish. The change to “main” was pointless and unnecessary. It’s almost like people want to find problems when there aren’t any.
I prefer main simply because it faster to type. I propose main branches be renamed to “m”
My main branch is called
HEAD.You monster.
I demand trunk because https://trunkbaseddevelopment.com/ is a great branching strategy guide that anyone should read. It also explains how to release code or fix it in a good way.
I like develop. Sounds nice and indicates things may be unstable.
I don’t think that’s a good idea it’s not descriptive enough in my opinion.
How about trunk to imply how to use it
Honestly I feel like people who had an issue with this were just as much making an issue out of nothing. I personally also think that “master” is just as much a normal and valid name as “main”, and to me the rename kinda felt like performative bullshit. But at the same time it’s just a name, if it makes people happy I don’t really care either. Nowadays I tend to use main, but it’s not something I really pay attention to.
🤨
Americans and their silly performative outrage
A form of art they have main-ered.
I guess masterpieces are now mainpieces
I like it, because it forced people not to assume
masteris the main branch. If something is common enough to almost be a standard, but it’s not actually a standard, it’s just waiting for disaster.These assumptions cause unnecessary breakage, but people will make them unless forced not to.
If something is common enough to be a standard it’s a standard.
And yet not everyone used to use
master, so scripts kept breaking for no good reason.Either make it a standard, or stop assuming it’s a standard. De-facto isn’t good enough.
Having a magical standard fairy waive a wand isn’t going to fix scripts, or stop them from breaking.
What? If there’s an actual standard, it will stop scripts from breaking, because the assumption that
masteris the main branch will always be true.I’ll find something else to screw up and cause it to break, don’t worry.