Add DOCUMENTER_KEY as ssh deploy key to tagbot #211
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
This should enable TagBot to also trigger documentation builds for the tagged versions, so that we would get a new stable version of the docs. See https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#GitHub-Actions
|
Thank you! |
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.
This should enable TagBot to also trigger documentation builds for the tagged versions.
This fix the problems of the generation of stable docs as noticed in #210.
I assume, that the DOCUMENTER_KEY is already generated, because the development version of the docs are working fine.
See https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#GitHub-Actions