fix(ci): publish demo without Jekyll - #135
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
1 participant
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.
Summary
Fix the GitHub Pages publication flow for the demo after #134.
The deploy workflow now succeeds in pushing to
gh-pages, but GitHub Pages is configured to publish fromgh-pages:/docs. The current workflow publishes the built demo at the root ofgh-pages, so the Pages build looks for/docsand then invokes Jekyll.The failing Pages run reports:
and fails in
Build with Jekyll.Changes
dist-demo/.nojekyllso GitHub Pages treats the output as pre-built static content.dist-demointogh-pages/docs, matching the repository's current Pages source configuration.This keeps the existing
gh-pagesdeployment model and avoids requiring a manual Pages settings change.