Repository navigation
Publish .nojekyll to bypass Jekyll on Pages branch deploys - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1.
The deploy workflow publishes the built site to the
gh-pagesbranch, and GitHub runs Jekyll processing on branch-based Pages deploys unless a.nojekyllfile is present. Jekyll silently ignores paths starting with_and adds avoidable build quirks. Adding the marker tostatic/makes Hugo emit it at the artifact root (public/.nojekyll), disabling Jekyll entirely for the published site.Verified locally: build copies it to
public/.nojekyll.