Fix docs deployment for tag pushes and add workflow_dispatch#664
Draft
Fix docs deployment for tag pushes and add workflow_dispatch#664
Conversation
The paths-filter skips tag pushes when the tagged commit already exists on main, silently skipping the entire build-docs job. This prevented v0.16.0 docs from deploying (stable still points to v0.15.0). Add a decide step that bypasses the filter for tag pushes and manual triggers. Add workflow_dispatch with a deploy_tag input so versioned docs can be rebuilt without re-tagging. Fixes #662
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
1 participant
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.
dorny/paths-filterskips tag pushes when the tagged commit already exists onmain, silently skippingdeploydocs(). This is whystablestill points to v0.15.0.Adds a
decidestep that bypasses the filter for tag pushes andworkflow_dispatch. Once merged, run the workflow manually withdeploy_tag: v0.16.0to fix stable.Fixes #662