ci/docs: Run on tagged releases only #1009
Merged
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 changes the ci/docs workflow
to only run on tagged releases by default
instead of every push to main.
This also updates the existing workflow_dispatch trigger to expect an input specifying the ref to publish docs from. With that, you should be able to specify a branch or tag from the Actions UI.
Example of how this looks from one of my projects:
Going this route has the disadvantage that
all documentation fixes and updates after a release will not be available on the website until another release or a manual publish which can accidentally also publish documentation for unreleased features.
Refs #1008