top | item 24289299

Set the default branch for newly-created repositories

28 points| jeamland | 5 years ago |github.blog | reply

13 comments

order
[+] samename|5 years ago|reply
Key highlight:

> On October 1, 2020, if you haven't changed the default branch for new repositories for your user, organization, or enterprise, it will automatically change from master to main. You can opt out of this change at any time

[+] kjeetgill|5 years ago|reply
To add emphasis to this: they changed the default branch name for new repositories.

You can opt-out of this change of the default. I don't know why I'd read that as changing existing repositories unless opted out.

[+] lxe|5 years ago|reply
Why not 'trunk'? It's a tree after all... there are 'branches'... SVN got it right.
[+] gkoberger|5 years ago|reply
Aside from the fact that `main` is pretty straightforward for people new to git, one huge benefit is that autocorrect for `ma` still works.
[+] derivagral|5 years ago|reply
I've been in software since I was a teen, and this comment finally made me realize what "trunk" was actually supposed to mean before Git took over.

https://xkcd.com/1053/

[+] wfriesen|5 years ago|reply
My guess is because "Main" was used in Microsoft's TFS.
[+] benatkin|5 years ago|reply
It's just like some politicians - destroying anything the predecessor created, no matter how good it is.
[+] philliphaydon|5 years ago|reply
I don’t know if it’s because I’m on my phone but I can’t opt out?

Edit: oh I miss read. Thought this affected existing repos.

Opted in for new repos.

[+] tomschlick|5 years ago|reply
Clicking "change default branch name now" just opens a form to change it, thats how you opt out by typing master in that form. It's not super clear.
[+] beirut_bootleg|5 years ago|reply
As a secondary developer, this offensive to me. Now I'll have to work on a branch named after the main developer, reminding me every day that it's THEIR project and I'm just a code monkey.