Could you please rename master branch and references to those in the code?

[ghost]

I see you have already implemented blocklist and allowlist. Would you be kind enough to change the master branch to some other branch?

Actually main might not be better - https://www.nakasendoway.com/the-japanese-family-system/

Other big projects have already moved to alternative or are actively moving.

Please see the statement from github's ceo here - https://twitter.com/natfriedman/status/1271253144442253312

Please help empower black communities and make tech inclusive.

Consider alternatives such as canary, develop or edge which are used by vercel/nextjs.

[kitsonk]

Why are you raising this with a relatively new account and spamming loads of repos with your request, intentionally hiding your identity?

I would only prefer to hear from long term community members, versus individuals who are going around trolling people.

[lucacasonato]

Yeah I agree with @kitsonk here. Creating an account to go around and open the same issue on all large repos on GItHub is not the way forward IMO.

Ref microsoft/TypeScript#39070, golang/go#39589, nodejs/node#33888, microsoft/dotnet#1217, sindresorhus/awesome#1793

[kitsonk]

And the account has been deleted.

[caspervonb]

Changing a few internal comments and variable names like in the recent patch by @lucacasonato which was trivial and had no observable outside effect is quite different from breaking away from git conventions which in turn breaks quite a bit of tooling that make assumptions about the master branch being the default untagged branch making it a non-trivial change.

I understand American's are going through some much needed changes right now which is probably where this is coming from but context of words also matter; having a master copy of something is about as offensive as having a master's degree in something.

[trivikr]

It looks like the author of this account was created for spamming, and has been deleted.

The Node.js core is considering renaming their default branch though, and initial discussions can be viewed at nodejs/node#33864

[kevinkassimo]

Adding my own personal opinion: IMHO the term “master” just by itself (without the presence of the other specific term) is probably fine: the specific word has other more positive meanings besides the controversial part (instead of following what was inherited by Git from BitKeeper). For example we also has the Master’s degree. Also when tracing back to word origin, technically “Mr.” is a weakened form of “master”.

However if the community overwhelmingly adopts “main”, “primary” or “leader”, I have no objection to change it.

[ry]

Regardless of the origin of the account - it's a valid issue and I'm sympathetic to the intentions.

If it was as easy as flipping a switch, I would do it. But we have a system of interrelated repositories that very likely will break in complex and mysterious ways if we renamed the master branch. I will wait for others to blaze this path. Maybe github will add some features to do this. Maybe there will be some blog posts describing how different systems managed it. But I really cannot afford to spend potentially days right now on this relatively innocuous issue.

Let's revisit in 6 months. Closing for now.

[NickMaev]

I see you have already implemented blocklist and allowlist. Would you be kind enough to change the master branch to some other branch?

Actually main might not be better - https://www.nakasendoway.com/the-japanese-family-system/

Other big projects have already moved to alternative or are actively moving.

Please see the statement from github's ceo here - https://twitter.com/natfriedman/status/1271253144442253312

Please help empower black communities and make tech inclusive.

Consider alternatives such as canary, develop or edge which are used by vercel/nextjs.

Actually that's not about software development.
Еveryone who sees something negative about technical terms should visit a psychiatrist, not GitHub. 🙂