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
What’s new from GitHub Changelog? June 2021 Recap
This month, we have some exciting updates to share. A lot of you have welcomed the improvements to your ability to sync a forked repo with upstream from the web UI, add video on issues
Introducing GitHub Copilot: your AI pair programmer
Today, we’re launching a technical preview of GitHub Copilot, a new AI pair programmer that helps you write better code.
Introducing the new GitHub Issues
Announcing new beta features for GitHub Issues for better planning and tracking of your projects in GitHub, including project tables, task lists, and issue forms.
