Conversation
m-houston
added this pull request to stack #299
September 24, 2026 16:22
m-houston
changed the title
m-houston
force-pushed
the
ccm-14750/release-check-report-rollup
branch
from
September 25, 2026 08:19
7fb3d80 to
82bee45
Compare
m-houston
force-pushed
the
ccm-14750/release-check-report-rollup
branch
from
September 25, 2026 08:22
82bee45 to
e2eb0c1
Compare
Extend release-check reporting so Jira and git comparisons are easier to act on. Add patch release rollups, Jira-aware command suggestions, and safer fix proposal output that preserves existing fix versions while keeping terminal previews readable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Make Jira key lookups resilient to deleted issues so multi-release reruns still complete and render missing keys as not found. Also align the README examples with the package script and published CLI entrypoints. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the inherited git commit extraction regression expectations aligned after the body-fallback change so the multi-release commit metadata remains asserted in the report-rollup slice. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
m-houston
force-pushed
the
ccm-14750/release-check-report-rollup
branch
from
September 25, 2026 16:48
e2eb0c1 to
5475267
Compare
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 top slice refines the reporting and operator guidance so the release-check tool is easier to act on in real governance workflows.
It includes:
Context
By this point in the stack, the tool can read release data, compare it with Jira, and optionally apply fixes. This PR improves how the results are presented so teams can understand governance gaps quickly and take the right next action.
That improves the practical reliability of ticket tracking for NHS governance by making the tool's output clearer at the point of use.
Why this is a separate slice
These are valuable usability and reporting refinements, but they are easier to review after the underlying comparison and fix behaviour is already established. Keeping them at the top avoids mixing presentation polish with core workflow logic.
Validation
Sensitive Information Declaration