docs: note exit-code behavior change in gw delete#101
Merged
Conversation
Single-target failures now exit with code 2 instead of 1, aligning with the multi-target batch contract introduced in PR #100. Surface this in README so users pinning exit codes in scripts can find it.
- Drop volatile "0.0.38+" version label; link PR #100 instead. - Clarify exit `0` covers the no-eligible-worktrees case in `-i`. - Generalize the script-author guidance from "target not found" to any failure (Skipped also covers busy / remove errors).
DaveDev42
force-pushed
the
docs-exit-code-note
branch
from
b6acbe8 to
be5610e
Compare
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.
Summary
## Notessection toREADME.mddocumenting thatgw deletesingle-target failures now exit with code2instead of1(aligning with the batch contract introduced in feat(delete): multi-target support with -i and --dry-run #100).CHANGELOG.mdis release-please managed, so the permanent note lives in the README. The 0.0.38 release PR body (chore(main): release 0.0.38 #99) is being edited in parallel to surface the same note for the upcoming release.Test plan
gw delete