|
Got an email that said:
We just tried it for the first time and the error message we received was 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. |
Replies: 10 comments 7 replies
|
I'm the user who was working through it. For reference I:
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. |
|
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 |
|
We're getting the same thing, would love to try this asap! We've been waiting months! |
|
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 Confirmed still not enabled as of Jul 17, before and after the "rollout completed" notes on the other threads:
To answer the original question ("how can I check if they've been enabled?"): the quickest signal I found is @skarim — could the |
|
@benjaminkomen enabled for the |
|
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 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! |
|
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.
|
|
Email sent! |
|
Hello. I tried contacting you on X with no response (so far, it's only been a day) but when you get a moment we need to get our organization/repo enabled. I put details in the DM. |
|
Confirmed working now — thank you @skarim! 🎉 |
|
@skarim — hitting the same issue, distinct from the org-handle-typo case above. Org: Confirmed server-side (not a CLI/cache issue) — No typo on our end that I can find ( Thanks! |
|
@matanzvili looked into this and the submission we had in the waitlist form was for |
|
Thank you 🙏 |
|
We are getting the same issue.
However when attempting to create stacks on openaustralia/righttoknow I get the following: |
|
Hi @skarim . I don't have X, so I'll write here :) |
I saw a button in a PR that asked if I wanted to stack the PRs. After doing that, my stack was also "stack-enabled" on the CLI side. Wierd? |
|
The issue on my end was resolved by using a classic PAT instead of a fine-grained token. It would be nice to get a clearer error message in that case. toolbox ex-1 [$]
❯ GITHUB_TOKEN=<fine-grained-token> gh stack submit
Checking stack state...
⚠ Stacked PRs are not enabled for this repository
? Would you still like to create regular PRs? (y/N)
ℹ Received interrupt, aborting operation
toolbox ex-1 [$]
❯ GITHUB_TOKEN=$GITHUB_CLASSIC_TOKEN gh stack submit
Checking stack state...
Submit cancelled — no branches were pushed |
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!