Live data from Hacker News

GitHub wil change default branch name from 'master' to 'main'

twitter.com

11–20 of 94 posts

Re: GitHub wil change default branch name from 'master' to 'main'

#14
post #8

If you read "master branch" and think of slavery, you have reading comprehension issues that won't be fixed by renaming the branch. (I know bitkeeper used master/slave terminology for repositories; that is completely irrelevant to git).

Given how even distributed systems used to use master/slave frequently, and some still do, and that people don't say "master branch" and typically just say "master", I think it would be surprising for someone to avoid that association if they are educated in computer sincere using those terms (which again many places do).

Also, it's not reading comprehension, it's subconscious level associations that people basically can't avoid.

Re: GitHub wil change default branch name from 'master' to 'main'

#18
post #10
post #4

Even existing projects??? No, that's not going to break tons of stuff and tooling built and running on production around "master" /s

Has someone said that's what they're doing? Have you seen more information about this change? Because the link here is just saying "that's a good idea and we're working on it" in response to someone asking about changing the default branch name. Like default sounds like new project creation time.

That's what I'm asking. I mean there are probably tons and tons of custom built tools, ci/cd's around the current default "master" branch. It would be awesome to wake up and see a ton of alarms and all builds and deployments failing, wouldn't it.

Re: GitHub wil change default branch name from 'master' to 'main'

#19
post #16

I saw a great point mentioned elsewhere on Twitter that an even better methodology is to use "prod" and "dev", as it makes the intent that little bit clearer.

But we already follow git-flow and have master, prod, staging and dev branches
Post reply on HN