A .nojekyll file tells GitHub Pages to not use Jekyll to build the website. It contains no data. Typically stores in the root directory.
To install, add a .nojekyll file to the /docs directory. Creat...
A .nojekyll file tells GitHub Pages to not use Jekyll to build the website. It contains no data. Typically stores in the root directory.
To install, add a .nojekyll file to the /docs directory. Create a new branch locally, named docs-config. Create an empty .nojekyll file. Use Git add to track the file.
Bypassing Jekyll on GitHub Pages is possible by creating a .nojekyll file in the repo root and push to GitHub. This may be needed if using files/directories starting with underscores since Jekyll does not copy these.
One way to add the file is to create it after Antora runs but before commit. For example: touch build/site/.nojekyll.
Instead, inject the file using Antora’s UI feature. Add a supplemental_files block under UI in the playbook.
NoJekyll plugin creates a .nojekyll file in the output directory. Useful when publishing to GitHub Pages to bypass default generator. Install with pip.
GitHub Pages allows publishing HTML in root or /docs. Disable Jekyll by placing .nojekyll there. This extension creates that file.
Putting .nojekyll in root tells GitHub not to use Jekyll. So need to build locally first for content in _site.
When GitHub sees .nojekyll, it serves index.html. Use /docs on master to keep source/output separate.
GitHub Pages
Git