Squashing and merging a stack is stuck

[mlaccetti]

Before:

After:

I've been stuck looking at these spinners for hours. Nothing is merging. I've cancelled and retried a few times; no luck.

[ace22b]

Same issue with rebase for me.

[andykenward]

Are signed commits required on your repos? I'm having the same issue.

[yannickgloster]

Running into the same issue in our repo as well

[borfast]

My repo does not require signed commits (it's the single one in the org like this, I believe).

The one outstanding thing I can think of is that the stack is based off a commit that is no longer the tip of main, and I'm trying to rebase + merge the stack without updating it first (because I don't want the approvals I have to be dismissed).

[nemith]

I've had the same problem. My repo doesn't require signed commits.

[yannickgloster]

Getting a new error on this now when I go to merge, with no explanation on why it's not mergable

[wolszews]

Getting a new error on this now when I go to merge, with no explanation on why it's not mergable

Same here. First day trying to use GH Stacked PRs and everything works fine but merge'ing (Squash and merge stack)

[MelDommer]

Getting a new error on this now when I go to merge, with no explanation on why it's not mergable

@yannickgloster @wolszews

If you have "require approval of the most recent reviewable push" setting on, this will always happen.

I turned that off then merging the entire stack worked.

[FrkAk]

Same problem, we have stack with everything ready, but both squash or merge does not work.

[sassomedia]

Luckily, for us it didn't get stuck when trying to merge the stack. However, it only merged the first (bottom) PR, then returned to "Ready" status for the other PRs.

Since only one PR got merged, the "Rebase Stack" button became available again, but upon trying to rebase, it reported conflicts. Yet, there were no conflicts, as a local gh stack sync rebased fine without issues. After the sync, the PRs were ready to merge again, but seemingly only one at a time. - Stack mergeing does not seem to work at this time.

[skarim]

x-posting from #256

Hey all, thanks for the reports. We've identified a bug where approvals are not being appropriately evaluated when merging a stack of multiple PRs. We're actively investigating and will update when we've released a fix.

In the meantime, you can get around this by merging one PR at a time. I know it's not ideal, but hopefully that will unblock your workflows in the short-term. Appreciate your patience!

[phillip-haydon]

The feature has not been released, guys. It's in closed beta, invite only, which means it's expected to be buggy. We just have to be patient.

You’re wrong. And even if it was closed beta it should be in a better state than it is. It’s completely broken and useless. It’s probably hands down the worst feature release GitHub has ever had. I would be embarrassed if I had worked on this.

[borfast]

@borfast that's not true as of yesterday, see https://github.blog/changelog/2026-07-30-stacked-pull-requests-are-now-in-public-preview/

I stand corrected. Thank you @alexharri .

You’re wrong. And even if it was closed beta it should be in a better state than it is.

@phillip-haydon I would disagree on the closed beta, since its whole purpose is to start getting feedback while still being able to make big mistakes. Public beta is a different story, and there I would agree that this is definitely not at a level for a public preview. The feature is pretty much broken and not useful, which is not expected of a preview - if it doesn't work, what are people going to preview? 🙂

[Happycoil]

There's also an issue about this problem: #323

[nemith]

Serious it is unusable as it and shocked to see it in public preview when the cor functionally doesn't even work.

If I try to use it I end up berating my coworkers with request to restamp already reviewed diffs.

The worst thing is I have been talking up stacked doffs and this announcement to others for months and now my reputation is as good as GitHub's when it comes to this feature.

Disappointed is an understatement and continues to show how much GitHub has fallen.

[nemith]

Also I reported this 22 days ago.

#168