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.

Sign up for GitHub

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

Update Master-to-Main-renaming-guide.md #7296

Merged
merged 1 commit into from
May 11, 2021
Merged

Update Master-to-Main-renaming-guide.md #7296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Documentation/Projects/M2MRenaming/Master-to-Main-renaming-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ Generate json data file describing Maestro migration, review it and disable all
## 2. Add `main` triggers to YAML pipelines

**Please read**
Before you get on with this step, you should know, that once you change the default branch in your GitHub repository ([step 5](#5-change-the-default-branch-to-main-for-your-github-repository), all open PRs targeting `master` will be retargeted and all PR builds will be triggered again.
Before you get on with this step, you should know, that once you change the default branch in your GitHub repository ([step 5](#5-change-the-default-branch-to-main-for-your-github-repository)), all open PRs targeting `master` will be retargeted and all PR builds will be triggered again.
This can cause a large strain on the engineering systems, so please consider the amount of opened pull requests in your repository.
Please consider - based on the heaviness of your PR build and the number of PRs - whether you want to disable the PR builds for the time being or not.

Expand Down