PR Tracker

What it is

A read-only list of every pull request the app's PR ledger tracks. Each row says, in plain words, whether the pull request needs its author to fix something, is ready to land, is waiting on a decision, is a draft, has not been checked yet, or is stuck, and who it is waiting on — the author's agent and how long ago it was told, the PR desk, the lander, or nobody yet. It only reads what the app already records, so it never merges, closes or comments on a pull request and never calls GitHub itself.

Where to find it

Dev Pipeline panel → Runs → the quiet line Every pull request and what it waits on, the same way the Auto-lander opens, with a back button to Runs. The line appears wherever the QA Fleet line does, because the PR ledger only tracks the Omniscio repository.

Along the top of the list are the same drop-down pills the Search window uses: Stage (tick one or more; each shows its count), Author, Waiting on, Age, Show (Open or Recently finished) and Sort (oldest first, newest first, recently changed), plus a search box and Clear filters. On a phone the pills fold into one Filters pill that opens a slide-up sheet ending in a Show N pull requests button.

How it behaves

The stages:

Stage	Means
Needs author fix	Conflicts with master, is behind master, has failing checks, or is held.
Stuck	Nothing has changed on it for three days while it waits on someone.
Ready to land	Mergeable with a clean merge state, already on master, or contained in another pull request. An owner "land" answer is shown as the reason on such a pull request; it never makes an unread one ready. A mergeable pull request whose merge state is blocked or still computing reads Not checked yet.
Waiting on a decision	The aged-PR queue asked about it and nobody has answered yet.
Draft	Still a draft.
Not checked yet	GitHub has not said whether it merges, and the cloud probe has not run on it.
Finished	Closed or merged in the last seven days. Shown only under Show: Recently finished.

The stage comes from the PR ledger's own GitHub reading, which refreshes every minute. The problem router's record and the aged-PR queue only add who was told and whether a decision is pending, so a missing side record never makes a pull request look healthier than it is.

The list loads 50 at a time with Show more, refreshes once a minute while it is open, and the search box waits a quarter second after you stop typing. When there is nothing it can honestly show it says so instead of an empty list:

• Pull requests are tracked on the operator's computer — this computer does not run the PR ledger.
• Not read from GitHub yet — this is the operator's computer, but the ledger's first read has not finished (a fresh start, or GitHub's request budget is spent).
• This list is not updating — the ledger has not checked GitHub for ten minutes; the rows are the last picture it took.
• Showing the first 5,000 — the read is capped; narrow the filters.

Limits: only the Omniscio repository is tracked, and there is no "being landed" stage, because nothing in the recorded data says reliably that a land is under way.

Related

The PR ledger page explains where the pull request records come from, and the PR Merge Queue page covers the separate AI-assisted merge board.