GitHub Community
-
|
It resets to the default xxx.github.io URL every time I update the site. I have to input the custom domain on the repository settings every single time I update the website. Any advice? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
|
When you configure the custom domain in the settings, it adds a CNAME file to the pages root. You must be force-pushing when you update your site. If you add a CNAME file containing the custom domain name to your pages root (or pull in the commit GH makes when you set the custom domain in Settings), you shouldn’t have this problem. |
Beta Was this translation helpful? Give feedback.
-
|
If you are using gh-pages to deploy your site, you can modify your package.json deploy command to: |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@flarsystem It looks like you started a comment here with a quote, but then the rest of your content didn’t come through. Was there more you meant to add here? |
Beta Was this translation helpful? Give feedback.
-
|
That is insane as any force push, even on a feature branch will break the entire website. Even if the default branch is not touched and the correct One can easily conclude that gh-pages cannot really be considered reliable as it can suddenly vanish. |
Beta Was this translation helpful? Give feedback.
-
|
I've just come across this. For clarity, commit a copy of the CNAME file to your build directory (in my case /public/CNAME). By the looks of it, each push is going to cause a rebuild of the contents of the gh-pages branch based on your pubic build directory. So if the CNAME file isn't committed to that public directory on your main branch, it will be wiped out. |
Beta Was this translation helpful? Give feedback.
-
|
Hello I have question |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
When you configure the custom domain in the settings, it adds a CNAME file to the pages root. You must be force-pushing when you update your site. If you add a CNAME file containing the custom domain name to your pages root (or pull in the commit GH makes when you set the custom domain in Settings), you shouldn’t have this problem.