[sentry]

Issue arguments that contain whitespace (such as agent input combining a short ID and a numeric ID, multiple IDs passed as one argument, or search queries) previously threw ValidationError: Invalid issue identifier: contains a space. via validateResourceId.

The parsing changes in PRs #1729, #1730, and #1747 (shipped in 0.48.0) addressed the underlying behavior by routing whitespace-containing inputs to issue search in single-issue parsers and splitting them on whitespace in multi-issue parsers.

This change adds regression tests in packages/cli/test/lib/issue-arguments.test.ts to ensure these cases (parseIssueArgument for searches like "CLI-1G1 7441717161" and parseIssueArguments splitting space-separated IDs) remain covered.

Fixes CLI-1G1

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 7, 2026 10:47am UTC

[sentry-junior]

Closing this as redundant. It only adds tests, and main already covers the same behavior.

• The bug is already fixed. CLI-1G1 is still being reported, but every recent event comes from 0.47.0 or older (the latest is 0.45.0, today). There are no events from 0.48.0 or 0.49.0, which fits with ref(cli): Parse issue arguments with their own grammar, before the command runs #1729, ref(cli): Parse dashboard and issue arguments with the shared ID grammar #1730, and ref(cli): Parse issue view, explain, and merge positionals before run #1747 having fixed it.
• Text with spaces is already treated as a search. test/lib/argument-conventions.test.ts checks this through parseIssueArgument for every issue command ("login timeout" → { type: "search" }). test/lib/arg-parsing.test.ts checks it for a numeric pair ("12345 6789" → search).
• Splitting on spaces is already tested. In issue-arguments.test.ts, "splits pasted IDs at newlines and spaces, keeping the order" covers the multi-issue split, and "parses each issue like parseIssueArgument" covers parsing each piece. That includes short IDs and numeric IDs.

The new cases repeat these checks with different strings. A failure they would catch is already caught by the tests above. Merging this would also mark CLI-1G1 fixed by a PR that changes no code.