Repository navigation
fix #5: publish each branch with its own site layout - #27
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
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.
Infrastructure only. Pin branch SHAs, build each full site in a separate read-only runner, then assemble static output using trusted main code and deploy in a separate Pages job. Branch templates, styles and scripts now appear in previews without merging schema/API changes. No triggering-check artifacts or fork code are consumed. PRs remain build-only. Seven tests and local production/API-branch assembly passed; the assembled API preview contains the compact schema directory, search and grouped versions. Same-origin previews remain limited to trusted same-repository contributors.