The same two people review everything
Post PRs to a team queue anyone can claim, and turn on per-person figures to see who is carrying the load.
The problem
Review requests go to whoever is quickest to say yes, or to the two seniors everyone trusts. They become the bottleneck, and nobody else learns that part of the code.
It’s hard to fix what you can’t see. Often nobody notices until one of them is away for a week.
The setup
- Add PullPro to Slack and connect your GitHub organization.
- Create public channels like the ones below.
- In the PullPro home tab, use Link a channel (then Link another channel) for each one.
- Open each channel’s settings and apply the settings on its card.
- Open a test PR and mark it ready for review (drafts aren’t posted). Once its checks pass, check where it lands.
Team review queue
#payments-reviews
Where every team PR waits for someone to claim it.
- Include: the PR author is a member of team
payments. - Review reminders: on, so unclaimed PRs come back to the whole channel instead of the usual reviewer.
- Reports: on, with granularity set to Individual, so the report shows review load per person.
Variations
- Pair it with a rotation, like a weekly first reviewer on duty, and use the report to check it’s working.
Good to know
- PullPro doesn’t assign or rotate reviewers. It makes the imbalance visible and claiming easy. The team still has to change who picks things up.
- Individual figures appear in the channel’s report for everyone in it, so say why you’re turning them on first.
In the docs: Customizing reports · The metrics page
Try this setup with your team
Free while in beta, with unlimited developers on every plan.