PR Linking on Board Items
PR linking on board items connects a Mission Control item to the GitHub pull requests that name it by ticket number, so the board shows the pull request's live status without anyone copying links. A merged pull request can move the item into the board's Done group automatically.
On this page
What it is
PR linking on board items is the bridge between a Mission Control board and GitHub pull requests. Every five minutes Omniscio reads the open pull requests of the repositories your connected projects point at, looks for item references such as MC-42 in each title and description, and records a link on the matching item.
The item then carries the pull request as a link and shows a status badge — Open, Draft, Merged or Closed — that follows GitHub. When a pull request merges, the item can be moved into the Done group without anyone touching the board.
The feature is one of the GitHub switches in Settings → Lab (the githubPrLinkingEnabled key) and it also follows the Mission Control checklist's "connect GitHub" answer, so a board that never asked for GitHub links is left alone.
Where to find it
- Settings → Lab → PR linking on board items turns the scanner on and off (
githubPrLinkingEnabled). - A Mission Control board item's Links tab lists the pull requests linked to that item, each opening on GitHub, and the item card carries the same status badge.
- Settings → GitHub holds the account and repository access the scanner reads with.
How it behaves
What it scans
Only open pull requests are fetched, at most 100 per repository, from the repositories of the projects that have a GitHub remote. Each pull request's title and body are searched for the item references of every board prefix currently in use (the default is MC), capped at 20 references per pull request.
A reference is recorded only when the number resolves to a real, non-deleted item on a board you can see. Re-scanning updates the same link instead of adding a duplicate, and a title edit on GitHub updates the label on the item.
Status badges and merging
The badge is derived from GitHub, not set by hand:
- Draft — a draft pull request.
- Open — open and ready for review.
- Merged — merged (GitHub's
merged_at). - Closed — closed without merging.
When a pull request's status becomes merged for the first time, the item is moved into the board's Done group if the board has one. The move is skipped when the item is already in Done, when the board defines no Done group, and when the GitHub auto-close preference is switched off — it is on by default and lives beside the other Mission Control GitHub settings.
Limits and failure handling
The scanner runs on the app's shared GitHub client, so its calls carry the same deadline, burst cap and rate-limit reporting as every other GitHub read. A rate-limited tick simply waits for the next one; a failed fetch logs and returns "no pull requests I could read" rather than inventing links. Failures in Omniscio's own linking work are logged separately, so a real bug cannot hide inside a quiet zero.
Related
Boards, items and how they are shared are described in mission-control.md and mission-control-part-2.md. Commits that reference items are the sibling surface in github-commit-linking.md, and every rule that reacts to a board change is in mc-automations.md. Every other page in this library is listed in INDEX.md.
Last verified 2026-11-10