ci: serialize release site publishing#228
Merged
Merged
Conversation
Build docs and example galleries as reusable workflow artifacts, then publish the combined site once after release preparation completes. Keep standalone publishing queued and align workflow names, scripts, and documentation.
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
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.
Summary
Why
Parallel example workflows previously pushed independently to the same website branch. Two jobs could start from the same branch state, causing one peaceiris/actions-gh-pages push to be rejected as a non-fast-forward update. The workflows also appeared as separate runs instead of jobs in the Release summary.
Validation