Conversation
m-houston
added this pull request to stack #299
September 24, 2026 16:22
m-houston
force-pushed
the
ccm-14750/release-check-git-notes
branch
from
September 25, 2026 08:22
16575fe to
0780b2d
Compare
Restrict explicit Jira key detection to commit subjects so squash-merge bodies do not create false governance associations, such as CCM-11990 being grouped under CCM-1190 or Dependabot rollups being linked to ADR-003 from file paths in the body. Co-authored-by: Copilot <[email protected]>
Prefer Jira keys from the commit subject, but fall back to the body when the subject has none. Ignore path-like body matches such as /ADR-003/ so release-check still catches meaningful body references without linking file paths as governance tickets. Co-authored-by: Copilot <[email protected]>
This branch has not been deployed
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
1 participant
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.
Description
This slice adds the git and release-note reading capabilities needed to identify what a release contains before we compare it with Jira.
It includes:
Context
For NHS governance, we need confidence that the tickets represented in a release can be traced from the source history into the release-check flow.
This PR keeps the scope to local release evidence only: it teaches the tool how to read what has shipped, but it does not yet call Jira or decide whether tracking is correct.
Why this is a separate slice
Git and release-note collection is the first real data source for the tool and is reusable by every higher layer. Reviewing it separately keeps the later comparison logic easier to follow.
Validation
Sensitive Information Declaration