Playbooks

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.

The problem

The fix blocking tonight’s release sits in the channel between a README tweak and a refactor.

How you pick those PRs out depends on your branching. If hotfixes merge straight into main, a label marks them. If you cut release branches, the target branch does.

The setup

  1. Add PullPro to Slack and connect your GitHub organization.
  2. Create public channels like the ones below.
  3. In the PullPro home tab, use Link a channel (then Link another channel) for each one.
  4. Open each channel’s settings and apply the settings on its card.
  5. Open a test PR and mark it ready for review (drafts aren’t posted). Once its checks pass, check where it lands.

Release lane

#releases

Urgent PRs, for whoever is shipping.

  • Include (hotfixes merge into main): the PR has the label hotfix.
  • Include (release branches): All pull requests, only if targeting these branches: release/*, hotfix/*.
  • Review reminders: on, every hour (the shortest interval).
  • Goals: a shorter Time to first review claim than your other channels.

Variations

  • There’s no branch exclude, so to keep release-branch PRs out of the team channels, limit those channels to main as their target branch.

Good to know

  • Target branches match the branch a PR merges into, not the branch it was opened from. A hotfix/login branch merging into main matches main.
  • With GitHub’s stacked pull requests, each PR above the first targets the branch below it, not main. A channel limited to main won’t receive them.
  • Reminders only go out during the channel’s working hours. Widen them if your releases go out in the evening.

In the docs: Include rules and target branches · Reminder intervals

Try this setup with your team

Free while in beta, with unlimited developers on every plan.