issue-pr-deploy-traceability

What problem does it solve?

It solves the problem of broken traceability between Issues, their implementing PRs, and the resulting Deploy/Releases, so you can quickly answer “where did that change go?”

Core Features & Use Cases

• Detect merged PRs that never produced a deploy/release tag: flags potentially undeployed merges by checking for release tags created near the merge time.
• Find open issues that appear stalled without implementation: identifies issues older than 14 days that are not referenced by any PR and aren’t explicitly skipped by risk-appropriate labels.
• Surface PRs that don’t reference an Issue: finds merged PRs that lack closes/fixes/refs linkage patterns or open PRs whose bodies don’t include the expected issue reference.

Use case: run it every Saturday 6am to audit the repo’s hygiene and ensure every “Fixes/Closes #N” ends up in a corresponding deployed/released change.

Quick Start

Run the repository audit named issue-pr-deploy-traceability and then follow its outputs to append the weekly traceability report to the configured Notion page while sending the one-line Pushover summary and escalation flags when thresholds are exceeded.