Dashboard › cli › Distillation
49c93edc-9dd6-4f07-bdbe-5d19cf6a718e["lore_tm_v1_cRJtlIJ1CQLkYesKIosCcDFB5l6ckYGaDQXgfMtt63o","lore_tm_v1_ivfqk6rOBTlouSucKxM5OPAhGDVn0lZuVwLoT8hxmyc"]
packages/cli/test/commands/issue/merge.func.test.ts: mergeCommand.func() deliberately performs its own cardinality validation. With 0 positionals and no --into, 1 positional without --into, or 0 positionals plus --into, it throws an error containing needs at least 2 issue IDs and never calls mergeIssues; the 1-positional case also includes a --into hint.packages/cli/test/commands/issue/merge.func.test.ts: sentry issue merge CLI-A --into CLI-B is accepted as a 2-issue merge; mergeIssues is called exactly once with org test-org, and the resolved --into target 10B is moved to the front as the preferred parent ahead of 10A.packages/cli/src/commands/help.ts: helpCommand has no flags of its own and declares an array positional whose element uses placeholder: "command", brief: "Command to get help for", and parse: String; the array declaration has no minimum.sentry help --json emits the full command tree as structured JSON, while sentry help --json <command> emits metadata for the specified command or group as JSON.commandPath.length === 0, helpCommand yields new CommandOutput(introspectAllCommands()); the branded banner is rendered only by formatHelpHuman, so --json never triggers the sixel probe or any terminal I/O for a banner that would be discarded.helpCommand resolves non-empty command paths with introspectCommand(commandPath) and always gets structured output in --json mode.error is thrown as new OutputError(result), allowing rendering through the output system while exiting non-zero; successful results are yielded as new CommandOutput(result).