-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename master
to main
#549
Comments
Maybe we can do the migration when the number of PRs is at its minimum to reduce the impact? |
Based on my experience with doing this, it doesn't have any impact on PRs itself (the target is automatically changed by github from master to main when doing the rename). From other projects where I did this, I have the following workflow:
|
Yep, I wanted to minimize the number of PR authors impacted to be as low as possible... |
Just to mention that you can have issues with PRs if the original branch or repo got deleted by the author (you can still use the GH cli to recover the commits and make a new PR). We had a few PRs like this on SciPy. Otherwise it was a smooth transition. GH provides an easy rename info toolbox on all forks. |
Description
We currently use the branch name
master
for this repository for historical reasons. However, the open source community has moved on from this, the GitHub default is nowmain
, there's no reason to usemaster
if it is offensive and there are non-offensive alternatives, andmain
is 2-fewer letters to type :-)Guidance
It looks like renaming a branch will automatically update all open PRs, so this shouldn't be too disruptive as long as our dev community knows to update their local branches: https://github.com/github/renaming
The text was updated successfully, but these errors were encountered: