fix(cli): render stack-squash validation errors via clap#1671
Conversation
|
This pull request is part of a Mergify stack:
|
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
3a3ab58 to
c756dce
Compare
6825213 to
b085db1
Compare
Revision history
|
c756dce to
c41b366
Compare
b085db1 to
9bf2df1
Compare
c41b366 to
bd031e8
Compare
9bf2df1 to
053fa29
Compare
Merge Queue Status
Required conditions to enter a queue
|
Merge Queue Status
This pull request spent 8 minutes 29 seconds in the queue, including 8 minutes 7 seconds running CI. Waiting for
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks
Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. Requeued — the merge queue status continues in this comment ↓. |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 7 minutes 19 seconds in the queue, including 6 minutes 54 seconds running CI. Required conditions to merge
|
After dropping the binary, print the exact command to enable tab completion for the detected shell ($SHELL): bash, zsh, and fish each get a ready-to-paste line; any other shell is pointed at `mergify completions`. The installer writes nothing into the user's shell dirs. A curl|sh installer that ships a single binary leaves shell config to the user, as rustup and starship do; writing completion files from it is both surprising and unreliable — ~/.zfunc is off zsh's $fpath by default. Man-page generation stays available via the binary for real packaging. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Depends-On: #1671
Route
stack squashargument validation throughclap::Error(ValueValidation) so failures render with the usage line and the
standard exit code, like other parse errors, instead of a bare
eprintln!+exit(2).Also correct the
--debugdispatch comment: the flag is consumed byinit_tracing()at startup, not by command impls.Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com