Skip to content

feat(features): manual PR match tag for Jira-less PR->feature association - #3

Open
puneetadlerqa wants to merge 2 commits into
mainfrom
feat/feature-pr-match-key
Open

feat(features): manual PR match tag for Jira-less PR->feature association#3
puneetadlerqa wants to merge 2 commits into
mainfrom
feat/feature-pr-match-key

Conversation

@puneetadlerqa

Copy link
Copy Markdown
Contributor

Adds an optional per-feature [KEY] match tag so PRs auto-associate to a feature without Jira. map_pr_to_feature falls back to a bracketed-tag match; settable at create + editable on the feature. Fixes: PRs left unmapped (poller never surfaces them) when no Jira epic.

The manual PR match tag required a bracketed form ([FINES]); teams naturally
write the bare keyword (FINES / fines / FINES:). Match the tag as a whole,
case-insensitive token instead — brackets, colons and spaces all count as
boundaries — so FINES/[FINES]/FINES: all map, while REFINES/FINESSE do not.
…) matching

The matcher now treats the match tag as a whole word (brackets optional), so:
- method string is 'tag:HOLDS' (not 'tag:[HOLDS]')
- 'feat(HOLDS):' now maps (bare keyword)
- added a whole-word guard test: 'FINES' must not match REFINES/FINESSE
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