Repository navigation
ci: Publish official docs after release is published - #4054
Merged
Merged
Conversation
After a stable GitHub release is published and uploaded to PyPI, build the official documentation and publish it with the existing doc-publish task. Configure git to use DOCS_PUBLISH_TOKEN so the workflow can push to altair-viz/altair-viz.github.io.
The docs publishing helper generated the website commit message after changing into the website repository, so it could reference the website repo HEAD instead of the Altair source commit. Resolve the Altair source HEAD explicitly with git -C before publishing docs.
joelostblom
changed the title
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.
After a stable GitHub release is published and uploaded to PyPI, build
the official documentation and publish it with the existing doc-publish task. Configure git to use DOCS_PUBLISH_TOKEN so the workflow can push to altair-viz/altair-viz.github.io.
This also ensures that the current commit on main is referenced instead of creating a new doc-related commit.