We have decided to unify the naming of our default branches to main. All new repos will already use this naming. Over the next couple of months, we're going to rename the branches in our existing repos as well. We're using GitHub's new tooling to make sure branch policies and PRs are automatically updated.
However, this still requires some changes from you as well. This announcement describes the process and what you need to do on your end.
Process
We'll start with a smaller list of repos and grow from there. Theses are the planned starting repos:
We're starting with a smaller list to ensure we catch all cases where we need to update corresponding configuration in our Arcade-based tooling (see this fantastic blog post on how we build .NET).
Once we have validated our checklist, each repo admin will rename the default branch at their own pace. We expect to complete all repos in the next couple of months.
We'll add a sticky issue to each repo when we're about to rename the branch. We'll do this a few days before and we'll leave it there for two weeks.
You don't need to update your PRs. If you submitted a PR against the old default branch, the GitHub tooling will automatically retarget 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:
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:
We have decided to unify the naming of our default branches to
main. All new repos will already use this naming. Over the next couple of months, we're going to rename the branches in our existing repos as well. We're using GitHub's new tooling to make sure branch policies and PRs are automatically updated.However, this still requires some changes from you as well. This announcement describes the process and what you need to do on your end.
Process
We'll start with a smaller list of repos and grow from there. Theses are the planned starting repos:
We're starting with a smaller list to ensure we catch all cases where we need to update corresponding configuration in our Arcade-based tooling (see this fantastic blog post on how we build .NET).
Once we have validated our checklist, each repo admin will rename the default branch at their own pace. We expect to complete all repos in the next couple of months.
What you can expect
We have a detailed guide you can find at https://aka.ms/m2m-dotnet. This is only the essentials.
We'll add a sticky issue to each repo when we're about to rename the branch. We'll do this a few days before and we'll leave it there for two weeks.
You don't need to update your PRs. If you submitted a PR against the old default branch, the GitHub tooling will automatically retarget 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:
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:
For a discussion, please use https://github.com/dotnet/arcade/issues/6825.