Deploy gh-pages directly from CI #36
Merged
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
gh-pagesdirectly from the main CI workflow instead of a separate workflow run.Pagesworkflow and artifact download path.Why
The repository deploys by pushing
dist/to thegh-pagesbranch, so using a separate workflow with artifact download adds latency and failure points. This change keeps deployment in the WASM build job onpushtomain, which already prepares thedist/content.Changes
.github/workflows/ci.yml: replace artifact upload withpeaceiris/actions-gh-pages@v4deployment onpushtomain..github/workflows/pages.yml: removed (no longer needed).Tests
Not run (workflow-only change).