Creating a Github pages repo as private will not work even after changing visibility

[chrislgarry]

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.

[welcome]

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.

[chrislgarry]

If there is a particular place to fix and make a PR, I'm happy to do so. Thanks!

[janiceilene]

@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 👀

[chrislgarry]

@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 🙆‍♂️

[felicitymay]

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.

[felicitymay]

The pages team have got back to me with the following explanation:

This is expected and the user could have enabled pages once the repository was made public by selecting a source branch for Pages in their repository settings. We enable Pages automatically only on push. Not on any other events (such as repository switches from private to public for instance).

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 docs repository) to see if this was explained here. Possibly it would be worth updating step 4 of Creating a repository for your site and Creating a repository for your site (Jekyll) to recommend that this is a public site, since GitHub Pages are displayed publicly. As well as avoiding GitHub Free users encountering your problem, it might also help other users reduce the chance of accidentally publishing private information to a public pages site.

[felicitymay]

I've raised #3262 to make the information about this on docs.github.com clearer.

[felicitymay]

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.

[felicitymay]

😁 https://pages.github.com/ now updated to suggest creating a public repository.

[chrislgarry]

@felicitymay @janiceilene thank you very much!