feat(subject): add --require-subject-pattern for regex enforcement#74
Merged
Conversation
Teams need traceability from commits to tickets — a generic regex check covers Jira keys, GitHub issue refs, and any custom convention without hard-coding a specific format. Add --require-subject-pattern REGEX (CLI), require-subject-pattern (config), and require-subject-pattern (action.yml input). Regex is compiled at startup; an invalid pattern causes exit 2 immediately. The check runs independently of --enable/--disable. Tests cover match, no-match, invalid regex (exit 2), and config-file resolution. Docs updated in README and the site. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
Coverage Report (Δ +0.0%)
|
||||||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Teams need traceability from commits to tickets — a generic regex check
covers Jira keys, GitHub issue refs, and any custom convention without
hard-coding a specific format.
Add --require-subject-pattern REGEX (CLI), require-subject-pattern (config),
and require-subject-pattern (action.yml input). Regex is compiled at startup;
an invalid pattern causes exit 2 immediately. The check runs independently
of --enable/--disable. Tests cover match, no-match, invalid regex (exit 2),
and config-file resolution. Docs updated in README and the site.