PRs needing review get lost
Split it into a feed anyone can follow and a short review queue per team.
The problem
Most teams start with one channel for every PR. It works until the channel gets busy. The PRs that need a reviewer scroll past between the ones that don’t, and people stop reading.
Cutting the channel down to review requests fixes the noise, but then nobody sees what the rest of the team is shipping.
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.
Feed
#eng-prs
Every PR, for anyone who wants to follow along. Nobody gets pinged.
- Include: All pull requests.
- Review reminders and Reports: off.
Review queue, one per team
#payments-reviews
Only the PRs this team needs to review. Reminders and the weekly report live here.
- Include: the PR author is a member of team
payments. If the team owns whole repos, use the PR belongs to repositorypayments-apiinstead. - Review reminders: on.
- Goals: set Time to first review claim, for example 4 hours.
- Reports: on, weekly.
Variations
- Keep dependency PRs in the feed but out of the queue with an Exclude rule on the review channel. See Dependabot and Renovate PRs flood your review channel.
- A small team can skip the per-team queues and run one review channel next to the feed.
Good to know
- The feed shows the same PR message as the queue, Claim button included. There’s no read-only mode.
- The feed posts no reminders of its own. Personal reminders, like a nudge to merge an approved PR, follow the PR rather than the channel, so they’re still sent.
In the docs: Routing settings · Reminders
Try this setup with your team
Free while in beta, with unlimited developers on every plan.