document admin bypass and auto-merge limitations

skarim · skarim · commit ace18c09b5b6 · 2026-07-25T13:05:59.000-04:00
diff --git a/docs/package-lock.json b/docs/package-lock.json
diff --git a/docs/src/content/docs/faq.md b/docs/src/content/docs/faq.md
@@ -152,6 +152,14 @@ If the stack is not linear (e.g., after changes were pushed to a lower branch),
 
 Every PR in a stack must meet the same merge requirements as a PR targeting the stack base (e.g., `main`): required reviews, passing CI checks, CODEOWNER approvals, and a linear history. All PRs below it must also meet these requirements. See the [Checks, Rules & Requirements](#checks-rules--requirements) section above for details.
 
+### Can an admin bypass merge requirements on a Stacked PR?
+
+Not yet — admin bypass is coming soon, but currently unavailable for stacked PRs. Admins can't merge a stack before its requirements are met, so every PR in the stack must satisfy its branch protection rules and required checks before the stack can land.
+
+### Can I enable auto-merge on a Stacked PR?
+
+Not yet — auto-merge is coming soon, but currently unavailable for stacked PRs, for both direct merges and the merge queue. You can't set a PR in a stack to land automatically once its requirements are met. Until then, merge the stack (or the part you want to land) yourself once its PRs are ready.
+
 ### How does merging a stack of PRs differ from merging a regular PR?
 
 Stacks merge from the bottom up. When you click merge on a PR in a stack, that PR and all unmerged PRs below it land on the base branch together; PRs above remain open, and the remaining stack is automatically rebased so the next PR targets your base branch directly. With a direct merge the group lands as a single atomic operation; through a merge queue the PRs enter the queue together and are evaluated individually, from the bottom up.
diff --git a/docs/src/content/docs/guides/ui.md b/docs/src/content/docs/guides/ui.md
@@ -77,6 +77,10 @@ Before a PR in the stack can be merged, the following conditions must be met:
 
 ![Merge box for a stacked pull request](../../../assets/screenshots/stack-merge-box.png)
 
+:::note[Admin bypass & auto-merge currently unsupported]
+**Admin bypass** and **auto-merge** are coming soon, but currently unavailable for stacked PRs. You can't enable auto-merge on a PR in a stack, and admins can't bypass the merge requirements to merge before they're met. This applies to both direct merges and the merge queue.
+:::
+
 ### Rebasing from the UI
 
 When the stack is not linear (e.g., after changes were pushed to a lower branch, or after `main` has moved ahead), a **Rebase Stack** button appears in the merge box. Clicking it triggers a server-side cascading rebase that:
diff --git a/docs/src/content/docs/introduction/overview.md b/docs/src/content/docs/introduction/overview.md
@@ -69,6 +69,10 @@ GitHub supports two merge methods:
 
 In both methods, the resulting commit history is the same as if each PR had been merged individually, starting from the bottom.
 
+:::note[Admin bypass & auto-merge currently unsupported]
+Admin bypass and auto-merge functionality are coming soon, but currently unavailable for stacked PR merges. A stack merge can only be triggered once all selected PRs meet their requirements. See the [FAQ](/gh-stack/faq/#can-an-admin-bypass-merge-requirements-on-a-stacked-pr) for details.
+:::
+
 ### Merge Methods
 
 Stacks support all three merge methods:
