How to release stacked pull requests safely

A stack is a set of related pull requests that split one large change into smaller ones, so each can be reviewed on its own and then merged together. GitHub made stacked pull requests generally available on 6 October 2026, on all github.com plans. This guide covers what that changes when you release, and a safe way to do it.

What GitHub says about merging a stack

Why releasing a stack needs care

A safe order

Doing it outside working hours

Everything above applies at night too, with one extra rule: pin the exact commit you approved. If someone rebases the stack or pushes after you schedule, the merge should be skipped, not shipped.

How Merge Scheduler handles stacks

Merge Scheduler merges with GitHub's asynchronous merge API, the one GitHub recommends. It does not treat a stack as one release: you schedule a pull request by its own head commit, and if that commit changes after you schedule, the merge is skipped and you schedule again.

In practice, schedule the lowest pull request in the stack. New repositories start with only their default branch allowed, so a pull request that targets another feature branch is not scheduled by accident. For several pull requests that must go in a set order, ordered releases (Pro) can wait for each deploy to go green before the next one merges, and the revert switch can roll back the earlier ones if a later one fails.

Do this in Merge Scheduler: Release a backend and a frontend in order

Related: Why a scheduled merge should pin the commit you approved · How to release a backend before the frontend (and roll both back)