Please rename the default branch from `master` to `main` to be more inclusive
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
The branch naming scheme is not very inclusive, and doesn't match the direction the industry is going.
Aside from the arguably most important reason outlined above, these terms are becoming less used and therefore increasingly less compatible as more communities move away from its use (eg [NIST], [Python], [Drupal], [Github] and [Django]. The usage of 'master' and 'slave' in hardware and software has been halted by the Los Angeles County Office of Affirmative Action, the Django community, the Python community and several other programming languages. This was done because the language is offensive and hurts people in the community [Django2]. Root operator Internet Systems Consortium also stopped using the terms [ISC].
-- ref: ietf - draft-knodel-terminology-13
Describe the solution you'd like
I'd like to see the default branch changed from master to main. We recently did this at the nextcloud/helm repo and it just required us to update our ci/cd workflows and do a quick update our documentation. Both were just a search and replace of the word master to main. Any users with the current branch bookmarked or hardcoded will be redirected when they actually go to the old link.
GitHub also has a guide here: https://github.com/github/renaming
Describe alternatives you've considered
We could also use another name for the default branch instead of master, like default or core or release or primary.
Additional context
If there's any help needed on this front, I'm happy to lend a hand :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching the repository's CI/CD workflows and documentation for references to master, then review GitHub's branch-renaming guide. Done means the default branch is changed to main and the relevant workflow and documentation references are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100