release docs as an archive #12243
Merged
release docs as an archive #12243
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
lunny
approved these changes
Jul 14, 2020
GiteaBot
added
the
lgtm/need 1
techknowlogick
approved these changes
Jul 14, 2020
GiteaBot
added
lgtm/done
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR add a step to the release process to generate and package docs.
I hesitate between this solution and editing the the docs pipeline in drone so let me know if you prefer these solution.
This solution is far from perfect because the result is a folder with html file that could be serve via a local server but will be displayed with broken style (but readable) if open directly (file:// protocol). Hugo, which is used to the generate the docs, doesn't support an offline export solution and the relative path management needed for that.
Fix #4086