jwir3 / jwir3/git-risk

Add ability to have multiple ticket regular expressions

Open
#14 0 comments 0 reactions 0 assignees View on GitHub
acknowledged enhancement
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

If a company uses multiple ticket types (e.g. when transitioning to a new system), then commit messages might need to have two or more specifications for ticket numbers. We should support this somehow.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing ticket regular-expression configuration and the code that examines commit messages for ticket numbers. Determine how multiple ticket types should be represented and combined, then verify that commits matching each supported expression are recognized without breaking the current behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.