I\'m running into a weird issue with GitHub pages. I pushed a new commit to my personal pages page maltzj.github.io, but the new article isn\'t showing up there. When I exec
In my case, my problem was after git push
my GitHub file was updating but not showing my website on GitHub pages.
Note: I was creating Website by React
Also, on the HTML project, I faced the same problem. In that case, I just did first of all git pull
and then git status | git add . | git commit -m"adding some content" | and git push
. It worked for me.
But in the React project
, it didn't work. I run this again on my cmd npm run deploy
then my React web application is showing on GitHub pages.
My suggestion is to try everything showing on this post comments. Because the solution to this problem is not one.
I had the problem of having an unverified email. The update worked for the first time, but it failed after that. A verified email is needed to trigger a GitHub pages build. Also a deploy key cannot be used for this, as it won't trigger a build.
Source: http://web.archive.org/web/20140712011932/https://help.github.com/articles/troubleshooting-github-pages-build-failures/
Disclaimer: this was the case in 2014. Don't know if it's still required.
I had the same issue, but in my case CNAME contained the correct domain name.
I think the problem had something to do with repository renaming I did before... The online name was different from local, although there were no issues on pushing and online files got updated - the live version did not.
After deleting the repository from the local machine and cloning it from GitHub again, the problem got solved.
In my case, I had another file with the same permalink
to the page that was not refreshing the content. Pay attention to that.
Go to your index.html file through your site (example.github.io/index.html) and then reload the page. Then you can go back to (example.github.io) and it should have updated. You can do the same with the master.css file, etc.
If it doesn't work, try reloading (github.com/example/example.github.io/[blob/master/]index.html) instead and it will have updated.
I had this problem this week and no solution worked. I don't use Jekyll, only pure static HTML. It just sat three days refusing to update.
Here is what I had to do to get it to publish again.
snapshot
branch from master
.master
branch to the last commit that is live. (Commits tab, green checkmarks indicate published commits)master
.curl https://example.com | grep SMOKETEST
master
again, removing the smoke test.snapshot
branch you need to get your unpublished changes back into master
(cherry-picking gives the commits new ids/hashes, avoiding the risk of anything having cached them from before).master
again.Note: It could be enough to force push to remove the commits that are stuck and getting them back again. The smoke test is almost certainly not required. Cherry-picking may not be required.