Stacked PRs enabled -- but not?

[nckswt]

Got an email that said:

Hi there,

We’re excited to onboard you to the private preview of GitHub Stacked PRs!

Stacked PRs has been enabled for all repositories under

We just tried it for the first time and the error message we received was Stacked PRs are not enabled for this repository.

How can I check if they've been enabled? Is there something I need to set manually for access? I'm wondering if this is tied to today's Github outage.

[patman3746]

I'm the user who was working through it. For reference I:

• Created new PAT since auth login wasn't working (likely just the API issue)
• brew upgrade gh
• uninstalled and reinstalled gh cli & went through setup steps again

Stack submitted in our repo, just not with any of the UI components, instead just being linked and not triggering the actions chain as if they were all going into our main branch.

[zswanson]

We're having the same issue - got the email today but it mentioned what appears to be our company enterprise name, not the actual org that our GH repositories fall under. Several of us have tested and we get the same Stacked PRs are not enabled for this repository error.

[Brayden-Parkinson]

We're getting the same thing, would love to try this asap! We've been waiting months!

[benjaminkomen]

Same issue here, and I think @zswanson has identified the root cause for our case too — the email named the wrong org.

Our onboarding email said Stacked PRs was "enabled for all repositories under Neurie", but our actual org is neurio (id 1187513). There is no neurie org on GitHub (GET /orgs/neurie → 404), so it looks like the enrollment was created against a misspelled/nonexistent name and neurio was never actually enrolled.

Confirmed still not enabled as of Jul 17, before and after the "rollout completed" notes on the other threads:

• gh stack submit → ⚠ Stacked PRs are not enabled for this repository (fails before pushing)
• GET /repos/neurio/installer-app/stacks → 404
• Swept all 52 neurio repos I can access — every one 404s on /stacks

To answer the original question ("how can I check if they've been enabled?"): the quickest signal I found is gh api repos/<owner>/<repo>/stacks — 404 = not enabled, 200 = enabled. gh stack submit is the authoritative check (it hits the same enablement gate).

@skarim — could the neurio org be enrolled explicitly (as you did for smartacteam in #189)? Env: gh 2.96.0, gh-stack v0.0.8, account benjaminkomen.

[skarim]

@benjaminkomen enabled for the neurio org ✅

[skarim]

Hey folks! Sorry about all the issues here! The original waitlist form had a "GitHub organization handle" field, so that's what we used to send out the invites. If there were typos or your account is on GHEC (custom host on *.ghe.com) then the access probably didn't go through.

Unfortunately, there's no way I can programmatically get that info so will need folks to reach out to me directly. Please drop your org handle as a reply to this, or if you don't want to share publicly you can email or DM me on X (info in my GitHub bio).

Apologies again and appreciate your patience everyone!

[nckswt]

Thanks for looking into this! Sadly, this isn't the solution for our problem, though glad it's helping others. I've double-checked, and there's no typo our organization name from the email we received.

gh api repos/<org>/<repo>/stacks --verbose shows a 200 response for us, but I still get the following error and I don't know how to debug it:

❯ gh stack submit
Checking stack state...
⚠ Stacked PRs are not enabled for this repository
? Would you still like to create regular PRs? (y/N) 

[zswanson]

Email sent!

[benjaminkomen]

Confirmed working now — thank you @skarim! 🎉 GET /repos/neurio/installer-app/stacks returns 200 and gh stack submit no longer errors. And thanks for the root-cause explanation; the "org handle field + typo" theory matches exactly what we saw ("Neurie" vs neurio). Appreciate the quick turnaround!