Skip to Content
Use casesApproval before merge

The deputy prepares it. You approve it with one tap.

Get the speed of automation with a person in charge. A deputy prepares a change, asks you for a decision with a summary and a link, and acts only after you answer. You can answer from Home or from a Slack message.

How it works

  • Trigger. Any trigger. This recipe uses a weekly schedule, so it extends Nightly dependency upgrades.
  • What the run does. It prepares the pull request, then asks you to approve it, and merges only if you say yes.
  • Who is contacted. The deputy’s owner. The question appears under Waiting on you on Home, and as a Slack message with buttons when your admin has connected Slack.
  • What you see. A question with your choices, a summary and a link to the pull request. Your branch protection rules still apply.

The run waits for you while the environment stays up, then parks and frees its CPU and memory while it waits. When you answer, the same run picks up where it stopped. See Timeouts and parking.

Set it up

  1. Follow the setup for Nightly dependency upgrades. Use a GitHub personal access token that is allowed to merge.
  2. Edit the mission’s prompt and replace it with the prompt below. Saving makes a new version.
  3. Select Dry run to check it.

What you should see: after the next scheduled run, a row under Waiting on you on Home with your choices. Answer it, and the run continues.

Example mission prompt

Update dependencies in the repository acme/web and ask before merging.

1. Update minor and patch versions on a branch, run the tests, and open
   one pull request.
2. Ask me for approval. Use the choices Approve, Needs changes and
   Reject. In the question, include a short summary of what changed,
   the test result, and a link to the pull request.
3. Wait for my answer.
4. If I approve, merge the pull request.
   If I choose Needs changes, comment on the pull request with what to fix.
   If I reject, close the pull request.
5. When you are finished, send me a heads-up with the outcome.

Make it yours

  • Use the same pattern for the stale sweeper: “Ask me before closing anything.”
  • Let a teammate decide. Make the teammate the deputy’s owner, or start the run by hand from their account.
  • Allow a typed answer, for example “Approve, but squash first”.
Issue triageOn-call helper