Twitter/X

@jessfraz tried GitHub's new stacked pull requests (public preview announced…

2026-07-30 · 18:22 UTC ·@jessfraz ·0 min read

Brief

Developer @jessfraz tested GitHub's newly announced stacked pull requests (public preview, GitHub changelog linked 2026-07-30) and found that enabling auto-merge with squash on the next PR breaks the stack: the series immediately unstacks. They report the issue directly and ask GitHub to fix it.

Why it matters

@jessfraz tried GitHub's new stacked pull requests (public preview announced 2026-07-30) and reports a bug when using auto-merge with squash on the "next" PR.

Key details

  • Using auto-merge + squash on the next PR causes the stack to immediately unstack; @jessfraz requests GitHub to fix the behavior.
Source evidence

tried it
cant use auto merge and squash on the next pr anymore
immediately unstacks
pls fix

GitHub (@github)

Took us a minute, but stacked PRs are now on GitHub 🥞
github.blog/changelog/2026-0…

Link

Stacked pull requests are now in public preview - GitHub Changelog

Stacked pull requests break large changes into small, reviewable pull requests. They’re an ordered series of pull requests that each represent focused layers of your change. With stacks, you can…
github.blog

— https://nitter.net/github/status/2082865588800504140#m