Rename master branch to main
See original GitHub issueThere’s a recent movement to replace “master” with a word that is descriptive while being absent the racist history of master & slave. This isn’t a new idea, however it’s gaining momentum on Twitter given the groundswell of action in the United States and globally after the police killing of George Floyd in Minneapolis two weeks ago. I stand with the protestors. 🖤
The language we use matters. Changing this for nock may be a minor pain but I think it’s mostly one-time and regardless seems well worth it.
There’s a tool here we could use for the PRs: https://github.com/ethomson/retarget_prs
@gr2m do you know if there’s any problem getting semantic-release to work with a default branch name that is not master
?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How to rename the "master" branch to "main" in Git
In case you are using the Tower Git client, you can rename branches very easily: After creating the new "main" branch on the...
Read more >How to rename the master branch to main
Rename master to main. First thing to do is to checkout the master branch if you didn't already: git checkout master # Also...
Read more >How to rename your "master" branch to "main" - GRRR Tech
From the branches page of your repository, you can rename the branch by clicking the little pencil icon. When renaming your branch, GitHub...
Read more >How to rename your Git master branch to main.
Change your default branch on GitHub by going to your GitHub repository in your browser, and navigate to Settings > Branches and click...
Read more >Why GitHub renamed its master branch to main
GitHub renamed the master branch to main for any Git repository, as it addresses cultural change like so many organizations that have nixed ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Let’s wait until we release nock 13, it would cause further merge conflicts and I’d need to make the edits in both
master
andbeta
note to self: we need to configure the branches setting for
semantic-release
. It is not looking formain
orlatest
by default, only formaster
. It’s something I’ll try to change withinsemantic-release
, but that will take a while.See https://semantic-release.gitbook.io/semantic-release/usage/configuration#branches