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.
The problem
The review is done and the PR is approved, and then it sits. The author has moved on to the next ticket, a conflict crept in, or CI went red after a rebase and nobody noticed.
Nobody is waiting on a reviewer any more, so channel reminders don’t help. The person who needs a nudge is the author.
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 channel
#payments-reviews
Any channel the PR is posted in. The DMs follow the PR, not the channel.
- Working hours: the team’s hours. Merge reminders only go out while one of the PR’s channels is in working hours.
- Ask everyone to link their GitHub account when PullPro offers. DMs only reach people it can match to a Slack user.
Variations
- Watch Time to merge on the metrics page to see whether approved PRs land sooner.
Good to know
- The merge reminder is sent once per PR, 12 hours after approval. The timing isn’t configurable.
- Only the author gets these DMs, and only if they’ve linked their GitHub account.
- Each person can turn merge conflict DMs off in their own notification settings.
In the docs: Merge reminders · Merge conflicts
Try this setup with your team
Free while in beta, with unlimited developers on every plan.