-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Renaming master
branch to main
#1277
Comments
A branch name should only affect our CI/CD. We should complete this ASAP. |
I think we need @Robbt to do the actual change. And that other maintainers (@paddatrapper) agree to do this change. |
This sounds like a good idea to me. I'm not sure what I need to do exactly to enact the change but I could figure it out. |
@Robbt Here you go https://github.com/github/renaming |
Weblate depends on the default branch name, it has to be updated once this is resolved. |
@Robbt Mayb I ping you for this one ? |
I'm up for doing this but don't want to break anything and haven't had much time to dive into the docs regarding the specific commands, but thanks for sharing them. @hairmare I believe could also do it, or we could elevate @paddatrapper to be able to make the change as well. |
I propose one of the admins do the changes and I make sure everything is working as expected and I will provide a PR changing the files still referencing master. Maybe promoting @paddatrapper would be a good idea ? Github is handling everything it there side with https://github.com/github/renaming#renaming-existing-branches. |
I opened up a discussion on the Adminstrator team on github to discuss giving @paddatrapper the owner role for the project so he could make these changes when they're ready. |
I propose to rename the
master
branch tomain
, guided by this draft's reasoning https://datatracker.ietf.org/doc/html/draft-knodel-terminology-05, specially this section https://datatracker.ietf.org/doc/html/draft-knodel-terminology-05#section-3.1.Tracking the draft : https://datatracker.ietf.org/doc/draft-knodel-terminology/
I am unsure of what will break after this change, but we can include this change before the v3 beta/stable release.
The text was updated successfully, but these errors were encountered: