Add GitHub Pages public web distribution - #7
Conversation
Build and validate the Leptos/WASM application at the repository project path, deploy tested main-branch artifacts through GitHub Pages, and document the public-release, persistence, and certification boundaries.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f1b3467c0f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: | | ||
| make check | ||
| python3 scripts/static_rust_sanity.py | ||
| python3 scripts/verify_manifest.py |
There was a problem hiding this comment.
Generate the content pack before verifying the manifest
In a clean GitHub Actions checkout, this command always fails because MANIFEST.sha256 requires dist/DGX_Lab_SLURM_Fundamentals_v1.0.0.dgxlabpack, while /dist/ is ignored and the file is not tracked; neither make check nor static_rust_sanity.py generates it. Consequently every Pages run exits here before the static build, upload, or deployment. Generate the pack first or exclude generated artifacts from manifest verification.
Useful? React with 👍 / 👎.
Summary
/DGX_Lab/project path, validates generated references, and deploys only testedmainartifactsValidation
/DGX_Lab/fixtureDeployment behavior
Pull requests build and validate the static distribution but do not publish it. Pushes to
mainupload and deploy the tested artifact.After merge
A repository administrator must select GitHub Actions under Settings → Pages once. The next successful
mainworkflow run will then publish the public web edition.