Skip to content

NO-ISSUE: accept NO-ISSUE in conventional commit scope#7

Merged
CalNightingale merged 1 commit into
mainfrom
CalNightingale/no-issue-scope
Apr 29, 2026
Merged

NO-ISSUE: accept NO-ISSUE in conventional commit scope#7
CalNightingale merged 1 commit into
mainfrom
CalNightingale/no-issue-scope

Conversation

@CalNightingale
Copy link
Copy Markdown
Contributor

@CalNightingale CalNightingale commented Apr 29, 2026

Summary

  • Add a fifth title-acceptance pattern so <type>(NO-ISSUE): subject is accepted, e.g. ci(NO-ISSUE): foo, feat(NO-ISSUE): bar.
  • The existing scope-with-Linear-ID pattern requires digits ([A-Z]+[-\s]\d+), so NO-ISSUE in scope was rejected. The other NO-ISSUE pattern only matches when NO-ISSUE is in the subject (e.g. ci: NO-ISSUE foo).
  • Repo-level docs (e.g. cloud_optimized_dicom/CLAUDE.md) instruct contributors to use <type>(NO-ISSUE): for ticketless changes, which previously failed this check.

Main use case

Dependabot-generated PRs in the COD repo

Accepted formats after this change

  • PROC-1234: subject (Linear ID prefix)
  • feat(PROC-1234): subject (Linear ID in scope)
  • NO-ISSUE: subject (bare NO-ISSUE)
  • ci: NO-ISSUE subject (NO-ISSUE in subject)
  • ci(NO-ISSUE): subject (new — NO-ISSUE in scope)

Test plan

  • Confirm existing valid titles (Linear ID prefix, feat(PROC-1234):, NO-ISSUE: ...) still pass.
  • Confirm ci(NO-ISSUE): foo now passes.
  • Confirm a title with no Linear ID and no NO-ISSUE (e.g. chore: random update) still fails.

🤖 Generated with Claude Code

The repo CLAUDE.md format `<type>(NO-ISSUE):` (e.g. `ci(NO-ISSUE): foo`)
was previously rejected because the scope-with-Linear-ID pattern
requires digits and the existing NO-ISSUE pattern matched only when
NO-ISSUE appeared in the subject. Add a fifth pattern so titles like
`ci(NO-ISSUE): foo` are accepted alongside the existing forms.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CalNightingale CalNightingale merged commit e3b0c27 into main Apr 29, 2026
1 check passed
@CalNightingale CalNightingale self-assigned this Apr 29, 2026
@CalNightingale CalNightingale deleted the CalNightingale/no-issue-scope branch April 29, 2026 16:31
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