Queue several pull requests for the night
You have a few pull requests ready and you do not want to be awake for each one. Queue them once: the first merges at the time you pick and each next one starts after the previous deploy is done. The queue is on Pro.
Build the queue
- Open Schedule and pick the first pull request. Pick a time, or use a quick time such as Tonight.
- Press Add a step and pick the next pull request. Repeat up to 10 steps. They can be in the same repository or in different ones.
- Put them in the order you want. Step 1 runs at the chosen time.
Pause between steps
By default the next step starts as soon as the previous deploy is done. For a step after the first, set "then wait" to 0 to 240 minutes if you want a gap, for example to watch your metrics before the next one goes out.
If a step fails
- Default: the queue stops. The failed step is reverted if auto-revert is on, and the steps that have not started are cancelled.
- Carry on: switch on "If a step fails, carry on with the rest". Use it when the pull requests are separate changes. A failed step is reverted or skipped and the next one still starts.
- Carry on is only offered when every step starts after the previous deploy and earlier steps are not reverted. A revert that does not work, or a cancel, always stops the queue.
Change the queue while it runs
- Open any step of the queue on the Releases page. A step that has not started has buttons: Start now, Change how it starts, and Skip this step. Each one explains what will happen and asks you to confirm.
- Change what happens if a step fails also works while the queue runs.
- If you merge one of the pull requests yourself on GitHub, the queue treats that step as done and carries on. The summary email says it was already merged by hand. Its deploy is not watched, and it is never reverted by the queue.
- When a queue has finished or stopped and none of its pull requests is merged, press Use this setup again. The Schedule page opens with the same steps and rules, and you only pick the time.
Good to know
- Each pull request is pinned to its commit, and every step is checked again right before it merges.
- Each step counts as one release on your plan.
- You get one summary email when every step is final.
- Another release due earlier on the same branch goes first. A release that is waiting shows its place in the line.
More guides: Release a backend and a frontend in order · Set up automatic revert for a failed deploy