consider renaming the primary branch
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
following github's default policy and its reasoning, we should consider renaming our primary branch, currently `master`, to something else, such as `main`.
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 reviewing GitHub's default-branch policy and the repository's use of the current `master` primary branch. Done means selecting the replacement name, renaming the primary branch, and ensuring repository references continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100