PR flow
The same pull request series for every team
Pull requests from the GitHub repositories linked to the workspace come in through sync and a signed webhook, and become three views: PRs merged per week, time from opening to merge, and open PRs with the age of each one.
Each metric shows its written definition alongside, the window used and what it cannot see. The calculation uses no AI: it is arithmetic on open, merge and close dates.
How it works
- Fixed 28-day window: PRs merged in the window, divided by four weeks.
- Time to merge at p50 and p85, from PR opening to merge; it measures waiting and review together.
- Open PRs that are not drafts, with the median age.
- Nearest-rank percentile: the number shown is always a value that actually happened.
- GitHub token stored encrypted, and a webhook with its own secret per repository, which can be rotated or removed.
- Synced PRs feed the delivery graph, which produces the delivery and DORA metrics.
Example use case
An engineering manager wants to know whether review became a bottleneck after the team doubled in size. She links the repositories to the workspace and, in the weekly meeting, the team looks at p85 time to merge and the open PR queue, with each number's definition on screen. The conversation moves from impressions to the PRs that got stuck.
What it does not do
- It only reads GitHub.
- Merges done outside GitHub, direct pushes to the default branch and PRs combined in a squash do not show up.
- Time to merge starts when the PR opens, not at the first commit.
- It does not measure people: the series are per repository and workspace.