One pull request dashboard for GitHub, GitLab, Gerrit and Azure DevOps.
Your open pull requests are spread across repositories, teams and providers. PR Flow pulls them into a single queue on your desktop and sorts it by one question: what needs you next?
A list of pull requests is not a dashboard.
Every provider already gives you somewhere to see open pull requests. What none of them gives you is an answer to the only question that matters on a Tuesday morning.
They are scattered by design
Repository PR lists are scoped to one repository. If your work spans a dozen services — or a monorepo plus three satellites, or GitHub for product code and Gerrit for the platform — there is no single page that shows all of it. So you keep tabs open, and the tabs become the system of record.
Notifications tell you what happened, not what to do
A notification feed is chronological and event-shaped: someone pushed, someone commented, CI went red. It is a log. Deciding what to work on means replaying that log in your head and reconstructing the current state of each pull request — which is exactly the work a dashboard should have done for you.
The important thing is rarely the newest thing
The review that has been sitting for four days blocking someone else's release does not bump itself to the top of anything. It just quietly ages while newer, louder items arrive above it.
“Waiting on me” and “waiting on them” look identical
Your own pull requests and the ones you were asked to review need completely different responses, but most views mix them into one undifferentiated list. So the question you carry around all day — where are they waiting on me, and where am I waiting on them — is one you answer by reading titles.
Requested changes come back on the author's schedule
You request a change on one pull request, another on a second, and go back to your own work. The authors push and reply hours or days later, in whatever order suits them. Nothing tells you which of those threads closed and which are still open, so “did that get done?” becomes a question you answer by reopening tabs.
Classify first, then rank.
PR Flow reads every open pull request, works out what state it is actually in, and orders the queue accordingly. The top of the list is the next thing that needs you.
Reviews you owe, above your own work.
Each pull request is classified — a review you owe, a thread you need to resolve, a green light to merge — and ranked from there. Reviews other people are waiting on surface above your own pull requests, because your own work is not blocked on you.
- A 4px left border encodes age: fresh, warm, stale
- Smart views: Needs you · Your PRs · Waiting on others · Recently done
- State chips for changes requested, unresolved threads and review requests
- Star a pull request to pin it to the top, or track any PR by URL
The ordering rules are worth understanding on their own — how the review queue decides what is next.
Enough context to decide, without opening a browser.
Open any row for the branch, diff stats, unresolved threads, an AI estimate of complexity, risk and review effort, and a full activity trail. Dependent pull requests are linked as a stack so you review them in the right order and never merge out from under one.
- Linked Jira, Linear and Trello tickets shown in context
- Thread summaries: what was asked, what was answered, what is still open
- Review, comment and approve or request changes without leaving the app
- One keystroke opens any diff line in your editor at the PR's branch
It connects the way each provider expects.
PR Flow normalizes pull requests, merge requests and changes into one model — but it connects to each provider on that provider's own terms, and keeps its vocabulary.
GitHub pull requests
Reads through your authenticated gh CLI session, so there is no extra OAuth app and no token to paste. Review requests, authored PRs and unresolved threads across every repository you touch.
GitLab merge requests
Reads through glab, including self-managed instances. Merge requests keep their own name and vocabulary rather than being relabelled as pull requests.
Gerrit changes
Connects directly to your Gerrit instance over its API with an HTTP password, and brings changes into the same ranked queue as everything else.
Azure DevOps
Native REST integration, configured with your organization URL, project and a personal access token stored in your keychain.
Any number of repositories
There is no per-repository setup step. Turn a provider on and the pull requests you are involved in show up, whichever repository or project they live in.
Issue trackers too
Jira via acli, Linear via linear-cli, and Trello — so a pull request shows the ticket it belongs to.
There is no server in the middle.
A hosted pull request dashboard needs broad, standing access to your repositories, and a copy of your code review data on someone else's infrastructure. PR Flow is a desktop app, so it needs neither.
- Requests go directly from your machine to your providers
- Your code, pull requests and diffs never touch PR Flow's servers
- Credentials you enter are encrypted in the OS keychain
- No product analytics or telemetry in the desktop app
The same principle covers AI: prompts run through a provider you configure, which can be a model on your own machine. See local AI code review, or the full security overview.
Scroll down it, or scan across it.
The feed is the default. When you would rather see the whole pipeline at once — during a release, or a review rotation handover — the same queue renders as a board.
Before you install it.
Is this a web dashboard or a desktop app?
Can it show pull requests from more than one provider at once?
How do I know whether a change I requested actually landed?
How does it authenticate?
Does it work with self-hosted instances?
Will it merge or comment on things without me?
Keep reading
GitHub pull request dashboard
Review requests, your own PRs and stale threads on GitHub, in one queue.
GitLab merge request dashboard
Merge requests across GitLab projects and self-managed instances.
Gerrit code review dashboard
Gerrit changes, patchsets and review labels alongside your other work.
Pull request review queue
How PR Flow decides which review needs you next, and why that beats a feed.
Local AI code review
AI review on your own provider — a CLI, a local model, or your gateway.
Point it at your real pull requests.
The queue only proves itself against work you actually have. Free for 14 days, no account or email required.