Update docs.yml: re-deploy docs when tag is pushed - #205
Open
garrison wants to merge 1 commit into
Open
Conversation
This PR changes the doc workflow to re-deploy when a (release) tag is pushed. This way, the reno release notes will reference the release once the workflow is complete. Previously, it required either manually re-running the workflow or pushing another commit to the release branch.
garrison
marked this pull request as ready for review
July 16, 2026 22:23
Coverage Report for CI Build 29539368612Coverage remained the same at 96.524%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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
2 participants
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 PR changes the doc workflow to re-deploy when a (release) tag is pushed. This way, the reno release notes will reference the release once the workflow is complete. Previously, it required either manually re-running the workflow or pushing another commit to the release branch.