Repository navigation
Conversation
Auto-merge works with stacked pull requests since they became generally available: https://github.blog/changelog/2026-10-06-stacked-pull-requests-generally-available/ Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AugnFjhMJiq9sxScLYogcu Co-authored-by: nicholas.dean <nicholas.dean@outset.ai>
|
This pull request only removes existing content. Before submitting a content-removal pull request, please open an issue explaining the proposed removal and wait for the GitHub Docs team to add the |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Why:
Closes: n/a, no existing issue
Stacked pull requests became generally available on October 6, 2026, and auto-merge now works with stacks: https://github.blog/changelog/2026-10-06-stacked-pull-requests-generally-available/
The article still says "Auto-merge is not supported for stacked pull requests."
What's being changed:
Removes that bullet from the note in the "Merge requirements" section of
content/pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md.Check off the following:
🤖 Generated with Claude Code