Live data from Hacker News

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

twitter.com

21–30 of 94 posts

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

#22
post #15
post #9

I feel like this will break a very significant amount of tooling

Now that consider all tools need to support new non-offensive terminology and old racist terminology used in existing projects

I'm saying that every tool/service that integrates with Github will now have to know whether the "default" branch is called master or main. Bugs will be caused by that and a lot of services will break.

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

#24
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).

To me when people are so angered that they can't separate contexts of language use, it's a signal or canary that things are out of control. And then reasonable people fold to requested or demanded change, like giving into a child rewarding them for something not reasonable, re-enforcing the illogical thought behaviour - doing it because it's easier to make satisfy a few angry, unreasonable people (perhaps a mob) who are associating language that has nothing to do with people in the context being used that they're changing.

Coddling will only lead to greater problems later, though yes, it certainly is a gesture showing respect — because of the improper associating, trigger it is causing an unreasonable mob. Coddling people makes them and society weaker, it doesn't strengthen them - it turns their anger into something other than critical thinking. Large for-profit corporations who are happy to jump to an easy decision like this seem to be more opportunists than leaders to make a statement like you said in response.

Political parties do the same, I can't remember what that's called though.

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

#26
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.

Plenty of projects on github don’t even have the concept of “prod” and “dev”.

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

#27
post #17

Is this related to master-slave? Master-slave in programming has nothing to do with humans, the contexts are separate. What's it say about society if people are unable to differentiate, separate the language in two contexts?

It says that our world has descended into utter madness.

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

#29
post #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…

If it's triggering underlying emotional trauma, then there's still unhealed/unprocessed trauma; rightfully so, though "actions speak louder than words" seems oddly fitting here.

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

#30
post #18
post #10

Earlier quoted context omitted.

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.

In that case. It's very likely to be done to existing projects.

Creating a different branch requires commiting to the repo, at least from what I understand.

And and branch name is just a text field.

Post reply on HN