Repository navigation
Move references from master to main - #318
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #313.
Updates what GitHub doesn't change when the default branch is renamed:
.github/workflows/ci.yml: the push branch filter runs CI onmaininstead ofmaster.tree/masterlinks indocs/README.md,docs/ioc/third-party.md,docs/samples.md,docs/ui-composition/index.mdanddocs/upgrade-guides/1.x-to-2.0.0.mdnow point tomain, and the contribution guide says to branch offmain.Merge after renaming
mastertomain: GitHub retargets this pull request tomain, so the merge commit is the first push tomainand checks that CI runs on it.The
release-1,release-2andrelease-3branches aren't changed: theirtree/masterlinks redirect.The commits aren't signed.