It is now possible to completely bypass Jekyll processing on GitHub Pages by creating a file named .nojekyll in the root of your pages repo and pushing it to GitHub. This should only be necessary if your site uses files or directories that start with underscores since Jekyll considers these to be special resources and does not copy them to the final site.
Related posts
New improvements in GitHub for Visual Studio
GitHub for Visual Studio 2.5.4 introduces new pull request improvements and easier navigation between GitHub.com and Visual Studio.
2016 Dodgeball Tournament: Play – Sponsor – Donate!
We’re looking forward to seeing you at the 2016 Dodgeball Tournament for friendly competition, team bonding, the chance to take home the OctoTrophy, and best of all, the opportunity to make an impact with local
Git 2.4 — atomic pushes, push to deploy, and more
Git’s 10-year birthday celebrations notwithstanding, the Git community has been busy preparing another major new release of the Git command-line utility. Release 2.4.0 is weighted towards cleanups, bug fixes, and other small improvements, but here
See what launched at GitHub Universe
Missed the main event? Learn more about everything that launched at GitHub Universe, from GitHub for mobile and a redesigned notifications experience to the GitHub Archive Program.
Read the day one keynote recapSecure the world's code, together
On day two of GitHub Universe, we announced GitHub Security Lab, bringing together security researchers, maintainers, and companies across the industry to secure open source.
Read the day two keynote recap