Stacked PRs are not enabled for this repository

[logansnow17]

Hi, we received the email today that all repositories in our organization have been granted access to the stacked PR private beta.

Stacked PRs has been enabled for all repositories under <our org>.

I tried using the CLI and got an issue saying that "Stacked PRs are not enabled for this repository"

(env) logan@l-work-laptop:~/proj/main$ gh stack sync spot/manage-domains-api
✗ current branch "spot/manage-domains-api" is not part of a stack
Checkout an existing stack using `gh stack checkout` or create a new stack using `gh stack init`
(env) logan@l-work-laptop:~/proj/main$ gh stack init
? Enable git rerere to remember conflict resolutions? Yes
? Set a branch prefix? (leave blank to skip)
? Would you like to use spot/manage-domains-api as the first layer of your stack? Yes
✓ Creating stack with trunk master and branch spot/manage-domains-api
You can continue working on spot/manage-domains-api
To add a new layer to your stack, run `gh stack add`
When you're ready to push to GitHub and open a stack of PRs, run `gh stack submit`


A new release of stack is available: 0.0.1 → 0.0.8
To upgrade, run: gh extension upgrade stack
https://github.com/github/gh-stack

(env) logan@l-work-laptop:~/proj/main$ gh stack add spot/manage-domains-page
✓ Created and checked out branch "spot/manage-domains-page"
(env) logan@l-work-laptop:~/proj/main$ gh stack submit
Pushing 2 branches to origin...
PR #130158 for spot/manage-domains-api is up to date
PR #130160 for spot/manage-domains-page is up to date
⚠ Stacked PRs are not enabled for this repository
✓ Pushed and synced 2 branches

I then tried updating since I saw I was out of date, but same error:

(env) logan@l-work-laptop:~/proj/main$ gh extension upgrade stack
[stack]: upgraded from v0.0.1 to v0.0.8
✓ Successfully checked extension upgrades
(env) logan@l-work-laptop:~/proj/main$ gh stack submit
Checking stack state...
⚠ Stacked PRs are not enabled for this repository
? Would you still like to create regular PRs? (y/N)

[skarim]

@logansnow17 apologies — it took a bit longer than expected for the enablement to roll out, but it has now been completed and everyone who received the email should have the feature enabled. Can you please retry and confirm if it works for you?

[logansnow17]

Thank you! Confirmed it is working for us now

[frank-lee-helion]

@skarim the "Stacked PRs are not enabled for this repository" error message is overused - we see it when no stack has been initialized and when there's a network error. Think this is the culprit? https://github.com/github/gh-stack/blob/v0.0.8/cmd/submit.go#L116-L120

Loving stacked PRs so far! Thank you so much.

[scottames]

@skarim we're seeing the same thing on our end, same simple workflow that logansnow17 outlined above:

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

We recieved the email yesterday, but the issue persists today. Is it possible there is another round of approvals we need to wait for?

[chlrbgh89]

@skarim We're seeing the same issue as well. We received the onboarding email stating that Stacked PRs had been enabled for all repositories in our organization, but gh stack submit still reports:

⚠ Stacked PRs are not enabled for this repository

We also checked the Stacks REST API directly, and GET /repos/{owner}/{repo}/stacks still returns 404 Not Found.

Could you confirm whether enablement is still rolling out to some organizations? We're happy to share the organization and repository details privately if needed.