A static site cannot by definition support PHP. Static websites serve content directly from the web-server’s file-system exactly as stored. Dynamic websites generate content live per each request. The request is delegated to a running web-application that builds the content. What is a Static Website You might be interested in PieCrust. It is a static … Read more
Create a dummy index.html at the root and put this in your header: <meta http-equiv=”refresh” content=”0; url=https://repo.github.io/folder/index.html”> Be sure to change the destination URL. This will instantly redirect from index.html to your folder/index.html.
A few years late, but I just implemented a simple redirect to support https://github.com/USER/PROJECT/releases/latest/download/package.zip. That should redirected to the latest tagged package.zip release asset. Hope it’s handy!
Nevermind, I solved it. If anyone has the same problem. GitHub Pages are case sensitive. Not only for folders, but also for image names.
You can have one site published to https://<username>.github.io by publishing to the master branch of a repository named “username.github.io” (substituting your actual username). You can also have an additional site per GitHub project published to https://<username>.github.io/<project>. Project settings let you choose which branch and directory to publish. A better description is available in the GitHub … Read more
TL;DR version: remote-tracking branch origin/master used to exist, but does not now, so local branch source is tracking something that does not exist, which is suspicious at best—it means a different Git feature is unable to do anything for you—and Git is warning you about it. You have been getting along just fine without having … Read more
I have a pair of scripts that do exactly this. In my situation, doc sources are in . (relative to where the scripts are run, of course), generated documentation is in _build/html, and I issue the commands touch _build/html/.nojekyll # disable GitHub’s Jekyll page generator ./commit-to-gh-pages.sh _build/html where commit-to-gh-pages.sh is #! /bin/sh # Commit the … Read more
As of December 27, 2009, you can completely opt-out of Jekyll processing by creating a file named .nojekyll in the root of your pages repo and pushing that to GitHub. This should only be necessary if your site uses directories that begin with an underscore, as Jekyll sees these as special dirs and does not … Read more
A bit late to the party but I just had this issue and my solution isn’t covered by any of the above. Specifically my issue was the following: I had created a github.pages site with a custom domain. I was pushing commits to the correct GitHub branch but not seeing the updates on the github.pages … Read more
From GitHub support, 2014-06-07: It’s not currently possible to manually trigger a rebuild, without pushing a commit to the appropriate branch. Edit: As Andy pointed out in the comments, you can push an empty commit with the command: git commit -m ‘rebuild pages’ –allow-empty git push origin <branch-name> Edit 2: Thanks to GitHub Actions, it’s … Read more