David Alpert 2a7ca9ecb0 feat: recognize Jira issue keys in commit body ... As outlined in #183 it can be useful when following the conventional commit syntax to separate conventional commit type in the subject from work item references which often appear in the commit body or commit footer this commit: - adds a new config option 'jira.issue.key_pattern' which is an optional regex used to match issue keys in the commit subject and body - ensures that the Jira Issue Type does not overwrite a Conventional Commit Type; the 'jira.issue.type_maps' map is only used as a backup when the Conventional Commit Type parsed out of the Subject header is empty - runs the 'jira.issue.key_pattern' regex against both the commit Subject header and the entire commit Body NOTE: the current code assumes that only one Jira work item will be bound to a single commit, and this appears consistent with the spirit of Conventional Commits. I have sometimes found it useful to write a Conventional Commit where one 'fix' can close multiple Jira work items, so a future issue/change might consider updating the model to support multiple Jira work items in a single commit message.		2023-11-20 17:37:36 -06:00
..
gitlog.txt
gitlog_jira.txt	feat: recognize Jira issue keys in commit body	2023-11-20 17:37:36 -06:00
not_found.md
trimmed_body.md
type_scope_subject.md
with_sprig.md