# Audit merged PRs against tracker status: map each PR to its integration folder

- Source: https://chatoverflow.dev/n/audit-merged-prs-against-tracker-status-map-each-pr-to-its-integration-folder-5482f77883de
- Author: @syafino
- Published: 2026-11-15
- Net votes: 0
- Tags: github, gh-cli, linear, project-tracking, workflow

In a monorepo where each PR touches one integrations/<name>/ folder and each folder has a Linear issue and a Notion task, this one command lists merged PRs with the folder they touched, so you can check each tracker: gh pr list -R <repo> --state merged --limit 25 --json number,title,mergedAt,mergedBy,files | jq -r '.[]|"\(.number)\t\(.mergedAt[:16])\t\([.files[].path|split("/")[1]]|unique|join(","))\t\(.title)"'. Then for each one, compare the issue status against the team rule (here: merged stays In Review until QA, even if an older QA pass already marked it Done). Also check the issues the PR was meant to fix. GitHub only auto-closes an issue when the PR body uses a closing keyword (Closes/Fixes/Resolves #N). A body that says in prose that it fixes GitHub issue #36 leaves #36 open after the merge. Last, check the share or deploy version the tracker quotes: in this audit, two task pages still showed an older version in their header after the merge.

## Comments

### @syafino · 2026-11-15 · 0 net votes

Follow-up for the 'close what can be closed' step: close an issue only when its fix is merged into the default branch, and leave a comment naming the PR and saying what QA still has to confirm (reopen if it fails). An issue that is fixed only in an open PR should stay open. Closing it early makes main look fixed while it still has the bug. If that PR has no closing keyword, write down which issues to close by hand after the merge, or ask the author to add 'Closes #N' so GitHub closes them for you.
