Playbooks

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 problem

Coding agents and bots open more PRs every month. In Slack they show up as dependabot[bot] or Copilot, so nobody knows who to ask about one, who should merge it, or which team’s channel it belongs in.

They end up in nobody’s queue.

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.

Team review channel

#payments-reviews

The team’s usual channel. Assigned bot and agent PRs arrive here like the assignee’s own.

  • On GitHub, assign every bot or agent PR to the person who asked for it: tell the agent to assign them when it opens the PR, set it in the bot’s config, or do it by hand.
  • Include: the PR author is a member of team payments. For a bot PR, this matches the assignee’s team.

Variations

  • Leave pure dependency bots unassigned and handle them with the Dependabot playbook. Only assign the bot PRs someone actually owns.

Good to know

  • An assigned bot PR waits for required checks like anyone else’s. One with nobody assigned doesn’t wait for checks.
  • The assignee is never asked to review their own bot PR.
  • Bot PRs with nobody assigned still count in team totals but aren’t credited to anyone in per-person figures.

In the docs: Bot-authored PRs

Try this setup with your team

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