DO NOT MERGE remove master branch #22
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.
DO NOT MERGE without asking. There are external changes that need to happen at the same time as this being merged.
the master branch is superfluous. This PR does the code prep needed to remove it. Instead of building the docs on pushes to master (which, incidentally, is fragile to people pushing to master outside of releases), this PR proposes we build the docs when a semver-compliant tag is pushed. If a tag is pushed by mistake, thus building the docs for the wrong point in the code, we can delete and redeploy the latest correct tag (taking care with associated github releases)
We'll also need to