Unified gh-pages creation
#5553
Open
+62
−47
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
Bullrich
force-pushed
the
ci/gha-migration/unify-gh-pages
branch
from
c04ecfd
to
6805ba2
Compare
This uses a `workflow_dispatch` event to nest a different action
Bullrich
force-pushed
the
ci/gha-migration/unify-gh-pages
branch
from
c148c01
to
a569efa
Compare
EgorPopelyaev
approved these changes
Sep 5, 2024
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.
Following @mordamax's advice to use
workflow_callevent, I ended up building a chain action.The action
publish-gh-pagesonly runs on the master branch and it will trigger thedocsactions.After it is done, it will fetch all the artifacts it uploaded and will use them to update the
gh-pagesbranch.Resolves paritytech/ci_cd#1026