feat(install): print how to enable shell completions#1675
Conversation
|
This pull request is part of a Mergify stack:
|
Merge Protections🟢 All 7 merge protections satisfied — ready to merge. Show 7 satisfied protections🟢 ⛓️ Depends-On RequirementsRequirement based on the presence of
🟢 🤖 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. |
e299829 to
2363101
Compare
bf0cbee to
cbbb1dd
Compare
Revision history
|
Route `stack squash` argument validation through `clap::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 `--debug` dispatch comment: the flag is consumed by `init_tracing()` at startup, not by command impls. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Change-Id: I86663735cc017dca638ff66ae0336d1e6d7b1b31
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> Change-Id: I9231ed40b44e96dc68f216f6820581cb71bfa579
2363101 to
f05dac8
Compare
cbbb1dd to
1fecbbb
Compare
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 8 minutes 21 seconds in the queue, including 6 minutes 48 seconds running CI. Waiting for
All conditions
ReasonPull request #1675 has been dequeued Queue conditions are not satisfied:
HintYou should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. Requeued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 7 minutes 7 seconds in the queue, including 12 minutes 31 seconds running CI. Waiting for
All conditions
ReasonPull request #1675 has been dequeued merge conditions no longer match. Blocked by:
HintYou should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. Requeued — the merge queue status continues in this comment ↓. |
The base branch was changed.
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 7 minutes 12 seconds in the queue, including 6 minutes 42 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