ci: allow release workflow to be triggered manually#6
Merged
Conversation
Adds workflow_dispatch with a tag input so a release can be cut without needing direct tag-push access to the repo; the release job already creates the tag if it doesn't exist via action-gh-release's tag_name input.
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.
Summary
workflow_dispatchtrigger to.github/workflows/release.ymlwith a requiredtaginput, so a release can be cut by manually running the workflow instead of needing direct tag-push access to the repo.tag_nameexplicitly tosoftprops/action-gh-release, which creates that tag (pointing at the dispatched commit) if it doesn't already exist.push: tags: v*trigger — that path is untouched.Test plan
tag: v0.1.11and confirm it builds all 4 platform binaries and publishes a GitHub Release at that tag.Generated by Claude Code