-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(ng-dev): make
new-main-branch
command more flexible to local setup
After we will perform the default branch rename, there are three scenarios for a contributor: 1. They manually fetch `upstream/main`, run `yarn` and then the migration tool. 2. They will not sync with upstream (as `upstream/master` does not exist), run `yarn` and then the migration tool. 3. They will manually update everything locally and in their forks. This bullet-point is just for completion (not something we bother about here). For (1): The `master` branch and `main` branch will locally exist. We should ask to delete the `main` branch switch back to `master`. Then continue with the full migration (with all other changes to the local git config) For (2): We should run the migration as is (e.g. fetch main and set it up locally).
- Loading branch information
1 parent
6ea40a1
commit f77a668
Showing
3 changed files
with
24 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters