Skip to content

Remove outdated auto-merge limitation from "Merging stacked pull requests" - #46411

Closed
nickpdean wants to merge 1 commit into
github:mainfrom
nickpdean:claude/stacked-prs-auto-merge-docs-rm35z8
Closed

nickpdean wants to merge 1 commit into
github:mainfrom
nickpdean:claude/stacked-prs-auto-merge-docs-rm35z8

Conversation

@nickpdean

Copy link
Copy Markdown

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:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

🤖 Generated with Claude Code

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>
@docs-bot docs-bot added the invalid This issue/PR is invalid label Oct 22, 2026
@docs-bot

Copy link
Copy Markdown
Collaborator

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 help wanted label to it. Once the issue has the help wanted label, you can open a new pull request that links the issue with Closes: #<issue number> in the description.

@github-actions github-actions Bot closed this Oct 22, 2026
@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Oct 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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 links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
pull-requests/how-tos/merge-and-close-pull-requests/merging-stacked-pull-requests.md fpt
ghec
fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This issue/PR is invalid triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants