master -> main #3126
Merged
master -> main #3126
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
|
Merged this PR and renamed the default branch of the Altair repository from |
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.
As discussed in #3124, this PR starts the process of migrating from
mastertomainas the Altair development branch.In particular, this PR updates the project's documentation to refer to
main. After merging this PR, we can use the GitHub interface to renamemastertomain(See https://github.com/github/renaming), and all of the open PRs will be updated automatically. It looks like I don't have permission to do this, so I expect @mattijn will need to be the one to make that change.Once the repo itself is migrated, we should each follow these instructions to update our local development environments to correspond.