feat(cli): add completion command - #1427
Open
MunifTanjim wants to merge 1 commit into
Open
Conversation
|
@MunifTanjim is attempting to deploy a commit to the Sentry Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit fc00641. Configure here.
MunifTanjim
force-pushed
the
feat/cli-completion-command
branch
from
August 14, 2026 16:05
fc00641 to
b76d690
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
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.

Why?
I like to manage my own shell setup, so I do this:
But currently there's no way to get the completion script without letting
sentry cliput it on the filesystem for me.Adding
sentry cli completioncommand solves that. It is a common pattern for most popular CLIs.Summary
Adds
sentry cli completion <shell>to print the shell completion script to stdout for bash, zsh, and fish. When no shell argument is given, the shell is auto-detected from$SHELL.This complements
sentry cli setup(which writes completion files to disk) by letting users and package managers install completions however they like:Details
packages/cli/src/commands/cli/completion.ts, registered under the existingcliroute group next tosetup/uninstall.getCompletionScript()generator (lib/completions.ts) anddetectShellType()helper (lib/shell.ts) — no new generation logic. Output is byte-identical to whatcli setupwrites.auth: false; unsupported shells fail with aValidationErrorlisting the supported shells.cli.md,SKILL.md,contributing.md) viapnpm run generate:docs.Testing
packages/cli/test/commands/cli/completion.test.ts— covers bash/zsh/fish output, the unsupported-shell error, and$SHELLauto-detection. All pass.tsc --noEmitandbiome checkclean.nonsenseerrors with a non-zero exit, andsentry cli --helplists the command.