Merging stack consistently fails with message: "auto-merge was automatically disabled / Pull Request is not mergeable" #256
Replies: 4 comments
-
CleanShot.2026-07-21.at.15.54.23.mp4I encountered the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
We are running into a similar issue. What are your branch protection setting? |
Beta Was this translation helpful? Give feedback.
-
|
Also having the same issue |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We're just starting to use stacked PRs, and have run into issues while attempting to merge our first stack from the GitHub UI.
Our stack consists of four small changes, which we have successfully stacked and approved. The topmost PR indicates that the whole stack is ready to merge.
However, when I attempt to merge the stack, I consistently see this experience:
All four commits start spinning, as expected.
All four commits switch to the purple "merging" state, as expected.
This message appears in the PR conversation:
All four commits revert to their pre-merge state.
I don't see any further information regarding why the merge failed, so am unsure what we should try to resolve the issue.
Beta Was this translation helpful? Give feedback.
All reactions