Repository navigation
Use Void's routing.trailingSlash instead of moving pages in CI - #20
Merged
Merged
Conversation
1.7.0 adds routing.trailingSlash, which the next commit uses. Its build also writes a .cloudflare directory, ignored here as Void's own scaffold does.
GitHub Pages answers /making/ only when making/index.html exists, so CI moved each built page into place. Void 1.7.0 writes that layout itself, and the output is byte-for-byte the same, so the post-build step goes.
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
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.
Void 1.7.0 adds
routing.trailingSlash, so the build writes pages asmaking/index.htmlitself and thefind … mvstep in CI goes.trailingSlash: trueand no workaround. All 726 files indist/clientare identical..cloudflareis ignored; 1.7.0's build writes it, and Void's scaffold ignores it too.🤖 Generated with Claude Code