Repository navigation
ci: publish the verified web app to GitHub Pages - #5
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
Publish the existing browser editor at https://gridaco.github.io/n3/ from successful
mainCI runs. The WASM lane builds and uploads an optimized production site; a dedicated Pages job deploys that same artifact only after all four verification lanes succeed. PRs and forks verify without publishing, and deployment permissions are limited to the Pages job.Add
just web-build --profile releasewhile keeping the localwebdevelopment profile as the default. Generated WASM, glue, and static files remain ignored build output; no deployment branch or generated commits are needed. Add the web app link to the README and document deployment ownership and retry behavior.Validation
/n3/in isolated Chromium: WebGPU startup, module/WASM paths, keyboard Insert, object creation, and Undo.just verifypassed through the repository pre-push hook. Hosted WASM and macOS checks passed; Linux checks and exact replay remain required in main CI before Pages can deploy.maindeployment branch. Live URL checks follow the first deployment.