Omniscio

GitHub Review Notifications in Mission Control

GitHub review notifications in Mission Control put the pull request's review state where the work lives: each reviewer on a linked pull request shows as requested, approved or changes requested, and a change raises one inbox alert naming the reviewer and the pull request.

On this page

What it is

GitHub review notifications in Mission Control extends PR linking from "the pull request's status" to "the pull request's review". For every pull request already linked to a board item, Omniscio reads that pull request's reviews and keeps one row per reviewer, so the item can show who has been asked, who approved and who asked for changes.

When a reviewer's state changes, one inbox alert is raised for that reviewer and that pull request. The same update replaces the previous alert for the same reviewer instead of stacking, so a busy pull request does not bury the inbox.

The switch is githubMcReviewNotificationsEnabled, off by default and listed in Settings → Lab; it also follows the board checklist's GitHub answer.

Where to find it

  • A board item linked to a pull request shows the current reviewers and their state; the review list is read per item through listItemReviews.
  • The inbox carries an alert such as "Review update on PR #42" with the reviewer's login and the review they gave.
  • Settings → Lab → GitHub review notifications in Mission Control is the on/off switch.

How it behaves

Which pull requests it watches

Only pull requests that are already linked to an item through PR linking are read. A link whose pull request is closed or merged is retired: its cached reviews are soft-deleted and it stops being polled. A pull request that disappears from view is not silently forgotten — its rows are only retired when GitHub's answer for that pull request was complete.

The five review states

State Meaning
pending the reviewer was asked and has not answered
approved the reviewer approved
changes_requested the reviewer asked for changes
dismissed the review was dismissed
commented the reviewer left comments without a verdict

A row is keyed on the reviewer's login inside one pull request, so re-reading a review updates it rather than adding a duplicate, and a person's newest review is the one shown.

Alerts

One alert is raised per reviewer per state change, with a deduplication key of board, item, pull request link and reviewer. That key is what makes the alert an update rather than a new notification each poll, and it is cleared when the state changes again. Reviewer logins appear in the alert text only — alerts are transient inbox items, not a stored profile.

Bounds and failure handling

The poll handles at most 50 pull requests per tick and gives its reads a shared 120-second deadline; when the deadline passes it keeps the work it has done and skips the rest to the next tick. If GitHub answers with only part of a pull request's reviews, that pull request keeps its cached rows rather than retiring reviewers the page did not carry. The whole poller has a kill switch (AMC_DISABLE_GITHUB_REVIEW_POLL) for emergencies.

The pull request that a review belongs to is linked by github-pr-linking.md, and the board it appears on is described in mission-control.md. Inbox alerts in general are in inbox-alerts.md. Every other page in this library is listed in INDEX.md.

Last verified 2026-11-10