add publish docs job to CI #26245
Merged
add publish docs job to CI #26245
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
arezaii
force-pushed
the
publish-docs-ghci
branch
2 times, most recently
from
3e44947 to
8202510
Compare
tzinsky
approved these changes
Feb 4, 2025
Signed-off-by: Ahmad Rezaii <ahmad.rezaii@hpe.com>
arezaii
force-pushed
the
publish-docs-ghci
branch
from
8202510 to
532a9d4
Compare
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 adds a new job to our CI process that will conditionally trigger on pushes to main. The new job depends on the
make_docjob finishing, and then it retrieves the documentation artifact from that job and uploads it to the website'smaindocs.It was necessary to include the hidden files when creating the artifact from the
make_docsstep so that the updated.htaccessfile would be included.Secrets are stored in github and are never exposed in logs etc.
Tested with bad docs (failed build) and adding new docs.
Set to use the
--dry-runoption for now. Once we've had a few days of it in place without issue and confirmed that the updates would be the same or better than our current update method, I'll remove that flag and it will begin actually publishing the docs.[reviewed by @tzinsky - thanks!]