Rename our main branch to 'main' #613
Merged
Conversation
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
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.
Once this PR has been merged,
mainwill be our main branch, rather thanmaster.We have many links to our documentation out in the wild, such as: https://github.com/diffplug/spotless/blob/master/plugin-gradle/README.md#license-header-options
Preserving the history of these links is an absolute must. For now, I will manually keep it parallel with
main, and I'll happily help anyone migrate any PRs against the deprecatedmasterto their new home atmain. Eventually I plan to build a tool to create an orphan commit atmasterwhich replaces every.mdfile, including anchors, with a link to the appropriately anchored place at our newmainbranch.