Skip to content

Add --dry-run option and recognize KEY-N: subject prefix#97

Open
oldium wants to merge 2 commits into
linear:mainfrom
oldium:dry-run-and-colon-prefix
Open

Add --dry-run option and recognize KEY-N: subject prefix#97
oldium wants to merge 2 commits into
linear:mainfrom
oldium:dry-run-and-colon-prefix

Conversation

@oldium
Copy link
Copy Markdown

@oldium oldium commented May 22, 2026

Summary

  • Add --dry-run flag (sync, complete, update) that runs the full git scan and read-only Linear queries but skips the create/update mutations; logs [dry-run] Would ... for the action that would have been taken.
  • Recognize KEY-N: subject prefix as a Linear issue reference, in addition to the existing [KEY-N], (KEY-N), and bare KEY-N forms. KEY-N:foo without a space after the colon stays unmatched, so the delimiter remains unambiguous.

🤖 Generated with Claude Code

oldium and others added 2 commits May 22, 2026 22:12
Lets users scan commits and call read-only Linear APIs (recent releases,
pipeline settings) without creating or modifying any release. Logs the
action that would have been taken.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
The bare-prefix common subject pattern previously required whitespace
immediately after the identifier (KEY-N foo). Allow an optional colon
before the whitespace so KEY-N: foo is also recognized, matching a very
common conventional-commits / Jira-style convention. KEY-N:foo (no
space after the colon) remains unmatched to keep the delimiter
unambiguous.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant