Skip to content

Say when to stack pull requests and how a stack lands - #2113

Merged
Kevinjohn merged 1 commit into
mainfrom
docs/stacked-pull-request-guidance
Nov 16, 2026
Merged

Kevinjohn merged 1 commit into
mainfrom
docs/stacked-pull-request-guidance

Conversation

@Kevinjohn

Copy link
Copy Markdown
Owner

What

AGENTS.md allowed targeting a predecessor branch for a stack without saying when a stack is warranted or how one lands.

  • Independent changes each branch from main; a pull request is based on another only when it needs that change's code.
  • A stack lands by merging each pull request into its base from the top down, then merging the bottom one into main once its checks pass.
  • Records why: the required check runs only for pull requests that target main, and changing a base does not start it.

Why

A 34-pull-request chain (#2079 to #2112) would have needed one CI cycle per pull request if merged bottom-up. Merged top-down it needed one.

Checks

  • Prettier on AGENTS.md: clean.
  • Documentation only; no code or workflow change.

Signed-off-by: Kevinjohn Gallagher <kevinjohngallagher@hotmail.com>
@Kevinjohn
Kevinjohn merged commit 9b6d210 into main Nov 16, 2026
5 checks passed
@Kevinjohn
Kevinjohn deleted the docs/stacked-pull-request-guidance branch November 16, 2026 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant