Repository navigation
Enabling merge queue hides the stack interface #349
Description
Activity
WHAT IS THIS GASLIGHTING the docs say Yes, Stacked PRs fully support merging via GitHub merge queue but when I enable the merge queue the stacks UNSTACK THEMSELVES and API says it never existed
(merge queue is enabled here) djeer@gl-air ci-test-repo % gh stack link 23 24 Checking existing stacks... ⚠ Stacked PRs are not enabled for this repository (i have disabled the merge queue) djeer@gl-air ci-test-repo % djeer@gl-air ci-test-repo % gh stack link 23 24 Checking existing stacks... Looking up PRs for 2 branches... ✓ Created stack with 2 PRs (stack #25) (i have enabled the queue again - prs unstacked themselves in the ui, trying to stack them) djeer@gl-air ci-test-repo % gh stack link 23 24 Checking existing stacks... ⚠ Stacked PRs are not enabled for this repositoryEnv:
gh-stack v0.0.8, org-owned private repo
queue enabled via classic branch protection or rule set - same effectReacted by Ibrahim Faruqi, tanjinpanna-tribe, Danai Antoniou, Stéphane Trebel and TomHey folks, apologies for the confusion here! We are doing a more gradual rollout of stacks for merge queue, so even if your org has access, it's possible that your merge queue repos do not. This gradual rollout will continue through August 14, at which point all merge queue repos will have access.
Reacted by Dima J, Vlad Tokarev, Axel8555, Matt Boardman and Sumit AgarwalReacted by Alek NowakHey folks, apologies for the confusion here! We are doing a more gradual rollout of stacks for merge queue, so even if your org has access, it's possible that your merge queue repos do not. This gradual rollout will continue through August 14, at which point all merge queue repos will have access.
We moved off of Graphite to GitHub Enterprise because this is clearly documented as supported and are now without the capabilities that Graphite offered. Is there any way to get on an early adopter list or anything @skarim?
Reacted by Ryan Hiebert and Dima JSame situation on
Maestro-Agentic-Inc/command-center(private, Enterprise Cloud).Symptom:
GET/POST /repos/.../stacks→ 404, andgh stack link/gh stack submitexit 9 ("Stacked PRs are not enabled for this repository"). Auth is OAuth (gho_), so this is not the PAT false-positive.Control: Every other repo in the same org returns
200on/stacks.command-centeris the only one with amerge_queueruleset rule (Main Protection), which matches the repro in this thread.We just moved merge path off Graphite onto the native merge queue (and our docs/CI assume stacks + MQ together). Is there any way to get this repo onto the MQ+stacks early-access list before the Aug 14 cutoff, @skarim?
Happy to help validate — we already have a 2-PR base-chained stack ready to
gh stack linkthe moment the API lights up.Same boat here, merge queue enabled, stacks are gone. 👎
This is a really poorly documented limitation relating to the public preview rollout of the Stacked PRs feature.
Given that merge-queue awareness/compatibility is one of the leading value propositions called out in the documentation for the feature (including announcement correspondence), it's very disappointing that I had to dig as much as I had to, just to find this Issue thread explaining the situation.
If the
ghCLI extension forstackscan't be simply improved to better guide early adopters that run into this issue, then surely at the very least, it should make an appearance in the gettings started/quickstart documentation and/or the troubleshooting material.Reacted by Scott Ames, jgao-gpsw, Tom Larcher, Patrick Richards, Thomas Bradford, Tim Camise and Artem LeshchevHey folks, apologies again for the confusion here. I agree this could have been communicated better and resulted in a poor experience, which was a miss on our part. Merge queues that use squash are inherently more complicated and so we're taking a more cautious approach, especially to ensure we resolve potential issues before expanding more broadly. Good news is that we have started the rollout and are on track to have this fully out by August 14th.
If you would like access sooner than that, please feel free to reach out to me directly and I can enable for your repo right away.
@dustinblanchard I've bumped up the
Maestro-Agentic-Inc/command-centerrepo on the list so it should have access to stacks nowHeya @skarim , I sent an email with the email listed on your profile to you requesting for our org to have it enabled.
If you don't recieve it or want me to send another way, please let me know!
Reacted by Sameen Karim
I just enabled the merge queue for my repo, and the stack interface went away. To confirm, I temporarily turned off the merge queue, and it put the stack interface back, so it seems clearly related to having the merge queue enabled.