Deploy docs for master separately - #1783
Merged
Merged
Conversation
Member
|
Why not use something to generate the tag name? Then this can also automate releases: https://github.com/rust-lang/rust-clippy/blob/master/.github/workflows/deploy.yml#L32-L37 Here's clippy's docs https://rust-lang.github.io/rust-clippy/ |
archseer
reviewed
Mar 13, 2022
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
2 participants
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.
Fixes #1607. Docs for master is now deployed at https://docs.helix-editor.com/master. The docs for 0.6 will have to be pushed to the
gh-pagesbranch manually, since the main docs are now updated only on releases.I'm think this should work, though I've not tested it.