Skip to content
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

Migration to main completed #182

Open
terrajobst opened this issue Apr 16, 2021 · 0 comments
Open

Migration to main completed #182

terrajobst opened this issue Apr 16, 2021 · 0 comments

Comments

@terrajobst
Copy link
Member

As previously announced, we have standardized the branch naming and use main as the default branch for all new repos moving forward. We have just completed the migration of all existing repos to main in the dotnet and aspnet organizations.

Migration status

What about non-Microsoft owned repos?

There are other repos in the dotnet organization that aren't owned by Microsoft. It's up to the project maintainers to decide whether or not they want to rename their default branch as well. We decided that there is a value in having a unified naming convention across all our repos as opposed to having a split like "new repos use main, existing repos use what they currently have". But renaming the default branch is work and there is a reason it took as couple of months to complete the migration to main.

In case you're curious, here are the steps we followed.

What do I need to do?

You don't need to update your PRs. If you submitted a PR against the old default branch, the GitHub tooling has automatically retargeted your PR against the new default branch (main).

For sanity, you should rename the default branch in your fork as well. When you go to your fork, GitHub will guide you through this experience:

Rename branch in fork

You will need to update the repos you cloned to your hard drive. When you go to the original repository, GitHub will guide you through this experience:

Update local repo

For a discussion, please use dotnet/arcade#6825.

@dotnet dotnet locked and limited conversation to collaborators Apr 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant