A better GitHub pull request dashboard for busy reviewers.
GitHub's pull request dashboard has improved significantly. PR Flow adds an attention-oriented layer across your review workflow — including GitLab and Gerrit — so you can see what actually needs your action next. It reads through your gh CLI session and lives in your menu bar.
PR Flow adds what comes after the inbox.
GitHub's redesigned pull request dashboard at github.com/pulls now surfaces review requests, fixes needed, ready-to-merge states, saved views and advanced filtering. That is a genuinely useful starting point for GitHub work. Two things remain out of scope for it.
It stops at the boundary of GitHub
If your review week also includes GitLab merge requests or Gerrit changes, those live in separate dashboards with separate workflows. PR Flow merges everything into one ranked queue — GitHub pull requests sit alongside GitLab and Gerrit work, ordered by what actually needs your attention next.
The notifications inbox is still event-shaped
A pull request that got three comments, a force push and a failed check appears as separate events, none of which says whether it is now waiting on you. Mark one thread as read and it disappears, whether or not you acted on it.
Who holds the ball?
PR Flow classifies each pull request by its current state: review requested from you, changes requested on your PR, approved and waiting for merge, or correctly idle. That classification — not arrival time — determines where it sits in your queue. A review request from Thursday stops being invisible just because newer rows arrived above it.
Unresolved threads as a signal
GitHub's unresolved review conversations are the most reliable indicator of who holds the ball next. PR Flow counts them on every row and surfaces them before you open anything, so a sprawling thread does not hide an open question from last week.
Your GitHub review state, resolved into one ranked list.
Two very different jobs, kept apart.
A pull request where you are a requested reviewer needs a decision from you. One you authored needs a nudge, a rebase, or nothing at all. PR Flow classifies each open pull request into the state it is genuinely in, then ranks reviews you owe above your own work — because your own work is not blocked on you.
- Needs you — review requested, or changes requested on your PR
- Your PRs — what you opened, and what is holding each one up
- Waiting on others — submitted, correctly out of your hands
- Recently done — merged and closed, for the weekly recap
Threads are state, not history.
GitHub's unresolved review conversations are the most reliable signal of who actually holds the ball on a pull request — and the easiest to lose in a long thread. PR Flow counts them on every row, and your AI provider can summarize a sprawling discussion into what was asked, what got clarified, and what is still open.
- Unresolved thread counts on the row, before you open anything
- Thread summaries for discussions that grew past reading
- Reply to a thread from the app, previewed before it posts
- Stack awareness links dependent PRs so you review them in order
A real GitHub review, from the menu bar.
The review view is a GitHub-style unified diff with per-file “viewed” tracking, line comments and thread replies. AI findings, if you enable them, appear as gutter pins you accept into a staged comment or dismiss. Pick approve, request changes or comment, then submit — and “Submit & next” drops you straight into the following item in the queue.
- Every write is previewed, staged, and logged locally
- PR Flow never merges — that stays a deliberate act on GitHub
- Press O to open any diff line in your editor
Three things, then it is running.
Install PR Flow
macOS, Windows or Linux. It starts in the menu bar or system tray. The 14-day trial needs no account, email or card.
Check your CLI
PR Flow reads GitHub through the session you already have. If this prints an account, there is nothing else to do.
Turn GitHub on
One switch in Settings. Your queue populates on the first poll and refreshes quietly in the background from then on.
Beyond what the native dashboard covers.
Stale reviews get louder
A 4px border on each row encodes age — fresh, warm, stale. The request from last Thursday stops being invisible just because newer rows arrived above it.
Digests instead of a live feed
A quiet OS notification at times you choose: what needs you, what has gone stale, and roughly how many minutes of review are queued up.
Nudges you preview first
When one of your pull requests is stuck on someone, PR Flow drafts a nudge to the right person. You read it before it sends. It is never automatic.
Working across more than GitHub? The same queue holds GitLab merge requests, Gerrit changes and Azure DevOps pull requests — see the full pull request dashboard.
GitHub specifics.
Do I have to give PR Flow a GitHub token?
Does it replace GitHub notifications?
Can I actually approve a pull request from the app?
Does it work with GitHub Enterprise?
What about repositories I only occasionally touch?
Keep reading
Stop triaging GitHub in a browser tab.
Install it, run gh auth status, and see what your real review queue looks like ranked. Free for 14 days.