-
Notifications
You must be signed in to change notification settings - Fork 59.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating a Github pages repo as private will not work even after changing visibility #2418
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
If there is a particular place to fix and make a PR, I'm happy to do so. Thanks! |
@chrislgarry Thanks so much for opening an issue! I'll triage this for the team to take a look at and figure out the best course of action 👀 |
@janiceilene thank you! Apologies for the lack of actionable data (logs, specific code responsible, etc.). Didnt have much time to chase it down. Hopefully it's pretty straightforward 🙆♂️ |
This comment has been minimized.
This comment has been minimized.
Hi @chrislgarry - many thanks for flagging this unexpected behavior. I'll check with the pages team on this and then we can work out the best way to document this limitation. |
The pages team have got back to me with the following explanation:
It sounds as if https://pages.github.com/ could do with a link out to a troubleshooting guide at the end to give tips like this. The content on that page is maintained in a different repository, so I'll forward your feedback on to the relevant team. I was looking at the https://docs.github.com site (which is published to from the |
I've raised #3262 to make the information about this on docs.github.com clearer. |
I'll raise an internal issue with the relevant team to ask them to amend https://pages.github.com/ so that this is clearer too. |
😁 https://pages.github.com/ now updated to suggest creating a public repository. |
@felicitymay @janiceilene thank you very much! |
So I'm facing the same issue, but slightly different: My repo was committed as public, github pages deployment was completely fine. I changed my repo to private (not realizing only public repos can be deployed), obviously the github page no longer worked. I then changed my repo back to public, and still my github pages does not redeploy. I even made a slight change to recommit, still doesn't work. So it sounds like my only solution is to delete my repo and recommit it only as public? This seems really cumbersome. |
Hey @magnussentio 👋 This question would best be handled by our support team. Please reach out to them. If there's anything in the documents that you have suggestions for updating, please feel free to open an issue. 💛 |
Hey @magnussentio - I have got in to the same issue . But i was able to resolve it by re-enabling the GitHub Pages in the repository's settings. it seems that the github pages settings on the repo is removed while making the repo private ( which makes sense) |
I made a website following the Github pages documentation, but accidentally made the repository private upon creation. Changing it to public afterwards, my webpage was still not visible. Documentation I've found states the repository must be public if you you're not a Pro user, however it doesn't mention it must be public upon creation time. My fix was to delete the repository and recreate it with public visibility upon creation. Something in the documentation stating this edge case would be helpful. I suspect changing visibility after the fact does not initiate DNS, hosting, etc.
The text was updated successfully, but these errors were encountered: