Pull Request Flow Analyser

The only metric that truly counts is whether your software delivery is winning you customers, making the team more efficient, or hitting the goals the business set. No chart here can answer that. But when the answer is no, or I'm not sure, the shape of your pull requests starts to paint the picture. This is simply a way to see what's going on.

WHAT YOU GET

Open PRs on the 1st

is the backlog growing, and how stale is it?

Opened · merged · closed

throughput per month, at a glance

Time to merge

how long merges took, same-day through over a month

Explore the full demo dashboard → demo data from a real project

ANALYSE YOUR OWN

Title optional: the repository or file name is used if you leave it blank

Repository

Read-only GitHub token

Create one on GitHub is pre-filled: read-only, pull requests only, expires in a day. Under Repository access choose Only select repositories and pick yours. Used once for this fetch and never stored.

Include lines-of-code stats (slower, but worth it for the size charts)

OPTIONAL · HELP US READ THE RESULTS

How do you think the project is going? 1 = badly · 5 = great

1 2 3 4 5

Anything you'd like to share about the project?

Email (only if you'd like someone to get in touch)

We never see your code or PR titles: just numbers, states, dates and line counts.

HOW THE FETCH WORKS

Paste the repository and a read-only token. The token link on the left opens GitHub with the minimal options already filled in.
We check the repository is visible, then fetch its pull requests in the background, and a progress page keeps you posted.
You land on a permalink you can share; the token is used for that one fetch and discarded.

Works for public and private repositories alike. Organisation repos need fine-grained tokens allowed in the org settings.

Only the newest 5,000 pull requests are fetched. On a long-lived repository, anything older is left out of the analysis.