v0.7.1: notify-cmd input for the GitHub Action - #11
Merged
Conversation
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
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
Exposes the v0.7.0
--notify-cmdhook to workflow users — patch release v0.7.1.notify-cmd, one command per line (newline-separated on purpose: shell commands may legitimately contain commas, unlike the comma-separatedlabelinput; a YAML block scalar makes multi-line natural). Each non-empty trimmed line becomes a repeated--notify-cmdflag, passed injection-safe viaenv:.notify-cmd: "echo smoke-notify", exercising the wiring on every PR (dry-run never fires notifications by design).SHA256SUMS.Test Plan
bash -nper file,shellcheckclean, 20/20 integration testsRelease steps after merge
git tag v0.7.1 && git push origin v0.7.1git tag -f v1 v0.7.1 && git push origin v1 --forcegh release create v0.7.1+ install smoke test🤖 Generated with Claude Code