GitHub Community
API #212771
Replies: 4 comments
|
Pro should work for this, Pages from private repo is ok and the site is still public. I think the upgrade is just not active on your account yet, thats why the API say free and Pages give error. Check Settings > Billing and plans, if it say Pro and you got the receipt email. Wait some hours maybe. If still free, contact github support about billing, we cant see your account here. After it show Pro, make repo private again and turn on Pages. |
|
Yes, Pro covers this. GitHub Pages can publish a public site from a private repo on a Pro plan, so once the upgrade takes effect your setup should work as you described it. The error message and the API both saying your plan is free are actually the same clue: the upgrade has not propagated to the part of GitHub that Pages checks yet. Pages reads the same plan record the API returns (GET /user shows it as plan.name), so until that flips to pro, Pages will keep refusing the private repo. What I would do:
Making the repo public again, as you did, is a fine temporary workaround, but you should not need to keep it that way once Pro is showing up in the API. |
|
That's what I was thinking happened. It just needed time to reflect. I
appreciate it.
…On Thursday, November 12, 2026, Praveen Suthar ***@***.***> wrote:
Pro should work for this, Pages from private repo is ok and the site is
still public. I think the upgrade is just not active on your account yet,
thats why the API say free and Pages give error.
Check Settings > Billing and plans, if it say Pro and you got the receipt
email. Wait some hours maybe. If still free, contact github support about
billing, we cant see your account here. After it show Pro, make repo
private again and turn on Pages.
—
Reply to this email directly, view it on GitHub
<#212771?email_source=notifications&email_token=BGQ2BFEQEC7URXTSLXLC3WT5YWQWPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVGYZTMOBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19563686>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGQ2BFD6XTNFYZG2JL7YZW35YWQWPAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMJSHA2TKNZRUF3AE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I ran a check on it again and this is what came back.
"The GitHub API still reports the account plan as **Free**. The read-only
request succeeded, and I didn’t change any settings.
That means the API has not yet reflected Pro. GitHub Support can confirm
whether the upgrade is still processing or the account needs attention."
If you can look into it would be much appreciated.
…On Thursday, November 12, 2026, Zabeeh Ullah ***@***.***> wrote:
Yes, Pro covers this. GitHub Pages can publish a public site from a
private repo on a Pro plan, so once the upgrade takes effect your setup
should work as you described it.
The error message and the API both saying your plan is free are actually
the same clue: the upgrade has not propagated to the part of GitHub that
Pages checks yet. Pages reads the same plan record the API returns (GET
/user shows it as plan.name), so until that flips to pro, Pages will keep
refusing the private repo.
What I would do:
1. Confirm Settings > Billing and plans shows Pro, and that you got
the receipt email.
2. Check the plan with gh api user --jq .plan.name now and then. When
it reports pro, try re-enabling Pages in the repo settings.
3. If it still reports free after a day or so, that is a billing sync
problem only Support can fix, so open a ticket with the receipt and the
repo name.
Making the repo public again, as you did, is a fine temporary workaround,
but you should not need to keep it that way once Pro is showing up in the
API.
—
Reply to this email directly, view it on GitHub
<#212771?email_source=notifications&email_token=BGQ2BFF5MCZBYPDKGQG44JD5YXO77A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVGY4TANRVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19569065>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGQ2BFHXRQHSEOP2ETCEDML5YXO77AVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMJSHA2TKNZRUF3AE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
None
Body
Hello GitHub Support,
I recently upgraded the phenixrhyder account to GitHub Pro. I’d like to keep my repository, phenixrhyder/formatr, private while keeping its GitHub Pages site publicly available at https://phenixrhyder.github.io/formatr/.
When I changed the repository to private, GitHub unpublished the Pages site. Trying to re-enable Pages returned: “Your current plan does not support GitHub Pages for this repository.” The GitHub API for my account also still reports the plan as free.
I’ve made the repository public again, and the site is currently live. Could you confirm whether GitHub Pro is active on this account, when the Pages/API access should reflect the upgrade, and whether Pro supports a public Pages site from a private repository?
Thank you.
All reactions