Add release.yml: automate docs release#78
Open
dwoz wants to merge 1 commit into
Open
Conversation
Triggered manually with workflow_dispatch(salt_version). Finds the open topic/release/* PR and runs the per-repo release steps.
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.
Adds a manually-triggered workflow that automates this repo's portion of the LTS release checklist.
Trigger:
workflow_dispatchwith inputsalt_version(e.g.3008.1)Steps:
topic/release/and merges it.v1.33→v1.34.0).mainwith message"v<salt_version> release". The existingbuild-sphinx-docs.ymlpicks up the tag and builds.Errors loudly if there is not exactly one open
topic/release/*PR.Branch protection / token permissions on
mainwill need to allow the workflow token to merge PRs and push tags — to be verified during a dry run.