Playbooks
Fixes for common PR review problems
Common review problems, and how to fix each one with PullPro.
PRs needing review get lost
Split it into a feed anyone can follow and a short review queue per team.
Dependabot and Renovate PRs flood your review channel
Exclude the dependencies label and bot-opened PRs from your review channel.
Bot and agent PRs have no clear owner
Assign each one to a person. PullPro then treats them as the author: named on the post, messaged when it needs attention, and routed by their team.
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.
Approved PRs sit for days without merging
PullPro nudges the author once a PR has been approved for 12 hours, and DMs them about merge conflicts and failing checks, the usual reasons approved PRs stall.
Reviews stall across time zones
Give each region its own channel and working hours, so reminders land during the day and review times are measured fairly.
Teams can’t tell which PRs are theirs
Route each team’s PRs to its own Slack channel, by GitHub team or repository, with its own hours, goal and report.
Urgent hotfix and release PRs look like every other PR
Give them their own Slack channel, by label or release branch, with a tighter goal and hourly reminders.
Not sure where to start? Try a feed and a review queue.