Until I discovered the awesome git checkout gh-pages // go to the gh-pages branch git rebase master // bring gh-pages up to date with master git push origin gh-pages // commit the changes git checkout master // return to the master branch I know this is old news to some of you (I’m a github n00b, struggling with basic stuff, so my advice is probably for other n00bs), but if I had read this a few months ago, it would’ve saved me big hassles, so I’m writing it for the others out there that are like me a few months ago.
Thanks @budparr @michael , Yes i am just hosting a jekyll website.
Updating that submodule to a commit that the build process can fetch will fix the build failure.
Ye are both correct, i dont really need a master branch Here's how to delete master branch for anyone interested: a new branch called gh-pages.
I was trying to replace the Automatic Page Generator content on a Github site with a Jekyll install last week and it seemed to never update. Everything seemed correct but the site would not update.
It seems that the better-simple-slideshow submodule points to a commit that is no longer available in the "leemark/better-simple-slideshow" repository on Git Hub.
In our logs the error looks like this: Unable to checkout '9d4365b029fa0ff761de08ed26adcf21716b16e9' in submodule path 'js/panes/slideshow/better-simple-slideshow' You should be able to reproduce the error by running "git submodule update --init" in a fresh clone of the repository.
I always loved Github’s ability to publish pages for a project and get the strain out of your server.
However, every time I tried it, I struggled to keep the gh-pages branch up to date.
For more information, see https://help.github.com/articles/troubleshooting-github-pages-build-failures. Got a response to the last time, I now find: Hi Tim, Sorry about the generic error message.
The full build logs are not available to users, but that is something we'd like to improve in the future.
But it never gave me any errors before recreating the gh-pages branch, it just wouldn't update.
file (something insignificant) and pushed to the gh-pages branch again.
Working for over a year now this way, now it just fails to show the updated site. GH recently updated to jekyll 3 and I think there was a change to the way future dates worked, maybe your post filename included a date that was in the future and was not being displayed because of that?