-
-
Notifications
You must be signed in to change notification settings - Fork 7
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 default branch from master to main #139
Comments
As a first step this needs some documenting of the impact of this. Apart from switching the default branch in git, what is assuming a branch named "master"? Probably the CI scripts, probably @GuillaumeGomez's release scripts. What else? Also how do we make sure that people actually notice this change and we don't get bug reports in a few months from people running from a completely outdated master branch? |
https://github.com/github/renaming/ sounds like github got us covered for many things. Some background information https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/. Looks like main will be the default in the majority of place pretty soon. Maybe it's less pain to do the change now. |
The default branch for cargo is |
The branch for |
Not for new projects, for projects using |
Yes I answered this in my comment too. Also, this change will probably be transparent for end users because GitHub redirects the branch https://about.gitlab.com/blog/2021/03/10/new-git-default-branch-name/ (also mentioned before.) |
Oh indeed, well, that's one less concern then. |
Progress with Rust 1.53
https://blog.rust-lang.org/2021/06/17/Rust-1.53.0.html#head-branch-name-support-in-cargo |
Should we then maybe do it before the release now? :) @GuillaumeGomez @bilelmoussaoui ? |
Sounds good to me |
Posting this in release since I think all repos should be changed.
Maybe do this before the hackfest such that we can fix everything that is affected by this during the weekend?
The text was updated successfully, but these errors were encountered: