GitHub Community
Project site while using CNAME on Org site #22933
-
|
I have an Org site at https://blog.poliastro.space with this repository: https://github.com/poliastro/poliastro.github.io/tree/master And a CNAME in my poliastro.space domain like this: https://mxtoolbox.com/SuperTool.aspx?action=a%3apoliastro.space&run=toolpage Now I’d like to setup this project site: https://github.com/poliastro/poliastro-benchmarks/tree/gh-pages But if I try to browse https://poliastro.github.io/poliastro-benchmarks it redirects to https://blog.poliastro.space/poliastro-benchmarks, which yields a 404. This is very similar to the issue reported here: But the responses there do not clarify my problem. In particular, according to a GitHub support person: > Yep the user.exmaple.com/projectname will automagically serve user/projectname gh-pages content. But apparently it’s not working in my case. Anything I’m doing wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi there @juanlu001, Thanks for being part of the Community Forum. I’ll help as best I can. If you’ve never published to GitHub Pages before from a particular repo, then things should magically start publishing when you create a If that still doesn’t do the trick, I’d recommend reaching out to private support at https://github.com/contact so we can dig a little deeper. Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Nadia, Thanks for your help! The repository was indeed properly configured, but to make sure I made a commit to gh-pages and… The pages appeared! Problem solved. Best, |
Beta Was this translation helpful? Give feedback.
Hi there @juanlu001,
Thanks for being part of the Community Forum. I’ll help as best I can.
If you’ve never published to GitHub Pages before from a particular repo, then things should magically start publishing when you create a
gh-pagesbranch. But if you previously selected some other branch that doesn’t exist anymore, you may have to go to the repo settings and selectgh-pageshere:If that still doesn’t do the trick, I’d recommend reaching out to private support at https://github.com/contact so we can dig a little deeper.
Cheers!