Rework website publishing workflow #8837
Merged
Conversation
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
The previous one turned out not to work because GH Actions lacked permissions to access an external repo from a script. The new workflow goes in two stages: 1. Generate website 2. Publish website Generate website stage does the following: 1. Check out the website repo and save all the snapshots in a separate directory 2. Generate the website from the current commit the CI runs against 3. Move the previous snapshots to the output directory of the documentation generation run Publish website step utilizes a 3rd party GitHub Action.
smarter
reviewed
Apr 29, 2020
nicolasstucki
approved these changes
May 1, 2020
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.
The previous one turned out not to work because GH Actions
lacked permissions to access an external repo from a script.
The new workflow goes in two stages:
Generate website stage does the following:
in a separate directory
against
the documentation generation run
Publish website step utilizes a 3rd party GitHub Action.