-
Notifications
You must be signed in to change notification settings - Fork 4
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
#4
Comments
+1 for switch to |
Lots of discussion in an old Slack thread. I'm +1 for switching across all repos given shared agreement on a process to minimize/address disruptions. |
+1 for switch to |
Thanks for that pointer.
Given the above discussion, I am not proposing or volunteering to undertake "across all repos" at this time 😁 I am gonna proceed with I'm also willing to track this overall and try to roll it out across more repos as time goes on. |
So, wrinkle: probably the best way to do this is renaming with the GitHub UI (because then there will be a redirect for any old URLs that point to Option nextstrain/private#1: somebody who has admin, do the work (I can still handle making the tickets and cleaning up any other No strong preference, just trying to keep this work moving forward… |
I vote |
@genehack Reposting from Slack, but I just updated your role in the Nextstrain organization to "Owner", so you should be able to choose Option 2 now. |
Renamed. Note that any existing checkouts will need to run the following commands in the working copy: git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a |
pathogen-repo-guide
and various other "modern" repos usemain
.Using
main
also aligns with currently recognized best practices in the broader open source community.From talking to folks, I understand this has caused some degree of disruption due to various places assuming
master
; I've also been cautioned to use@
as a branch label to ameliorate this.Opening this as a place for discussion on what direction to go with
yellow-fever
.The text was updated successfully, but these errors were encountered: