Dashboard › cli › Distillation
893af016-3d17-462b-952c-d2aa43755e7f["lore_tm_v1_wh0N6osM6LIdku60sHn5pw6FY-XG2B1ewHMONBiXD30","lore_tm_v1_wVG0s5Y2kalJb0gaVRNUnqudd6nT1Fn3jBaT4uZjTm8","lore_tm_v1_yp0JPBDeiVyZdokNy6SI9JfhMIrcZmBH5cJN3ADnpdg","lore_tm_v1_-p0t2iFwQJK3gWb8BahGaD5FjpuotExGGiruwrghNus","lore_tm_v1_LEVVNy_4MoNoP8wod8PeSjV-vRcx09W11FneqSdecYo","lore_tm_v1_FrBURLtg9E31jSnn5Ec70LhegAk77aHX-ybu7rJn0Bg"]
--into always designates an issue that participates in the merge as the preferred parent. In packages/cli/src/commands/issue/merge.ts, flags.into is appended to positional args via const effectiveArgs = flags.into ? [...args, flags.into] : args; duplicate representations are later collapsed by numeric-ID deduplication in resolveAllIssues.packages/cli/src/commands/issue/merge.ts lines 252-339 define mergeCommand: it merges 2+ issues, requires all issues to belong to the same organization, supports only error-type issues, and treats --into/-i as a preferred canonical parent rather than a guarantee because Sentry may select a larger group by event count.mergeCommand validates effectiveArgs.length >= 2; with one positional issue it suggests sentry issue merge CLI-K9 --into CLI-15H, while with none it gives sentry issue merge CLI-K9 CLI-15H CLI-15N. The displayed count in the error uses args.length.resolveAllIssues(effectiveArgs, cwd), mergeCommand calls orderForMerge(issues, flags.into, cwd), maps ordered issues to numeric groupIds, calls mergeIssues(org, groupIds), maps returned IDs back to short IDs, and warns when raw.parent differs from requestedParentId.packages/cli/src/commands/issue/merge.ts lines 245-249 throw ValidationError with field "into" when --into does not match any provided issue, including the provided short IDs in the message.apps/cli-docs/src/content/docs/commands/agent-conversation.md documents sentry agent-conversation list [<org>] and sentry agent-conversation view [<org>/]<conversation-id>. List options include --limit default "25", --period default "7d", --query, --fresh, and --cursor; all commands support --json and --fields.field when constructing a ValidationError; unfielded validation errors collapse into one Sentry fingerprint.packages/cli/src/lib/errors.ts distinguishes error classes by cause: ContextError for an omitted required value, ResolutionError for a supplied value that cannot be matched, and ValidationError for malformed input.ContextError requires a single-line CLI usage example, defaults to DSN/project detection alternatives when alternatives is omitted, treats explicitly supplied alternatives including [] as a required-context case, and throws a developer-time Error if command contains \n.buildValidationMessage(headline, examples, note?) formats a validation headline, optional Try: examples, and optional Note: diagnostic context. validationError(headline, examples, field?, note?) wraps that output in new ValidationError(..., field), although its current field parameter remains optional in the type signature.92dc1dab246fa60438667cd8e449426968bf84a6 — fix(docs): correct agent conversation argument syntax, authored by alicandayan <268751452+alicandayan@users.noreply.github.com> and committed by Burak Yigit Kaya <byk@sentry.io>; 2. 285a589de9aae902718f18b33a3f13ee0bdef8d7 — fix(docs): derive command references from metadata, authored and committed by Burak Yigit Kaya; 3. fc5d50e2324e2b6bb2067976bf1515dab45224fb — fix(ci): skip risk labels for fork PRs, authored and committed by Burak Yigit Kaya.