fix(pages): self-enable Pages in the deploy workflow (first-run 404) - #28
Merged
Conversation
The GitHub Pages deploy failed on the first run (the #27 merge) at actions/configure-pages@v5: "Get Pages site failed ... Error: Not Found" — the action read the Pages site before Pages was enabled with the GitHub Actions build type. Add `enablement: true` so configure-pages turns Pages on via the API if it isn't already, making the workflow self-sufficient and idempotent. Merging this re-triggers the workflow (touches the workflow path), which then publishes deploy/wasm-web/ to https://liujonathan24.github.io/NetHackHarness/. Claude-Session: https://claude.ai/code/session_01D3HuJeFjkPti8RgmT88joG
liujonathan24
had a problem deploying
to
github-pages
July 15, 2026 20:15 — with 
GitHub Actions
Failure
GitHub Actions
Failure
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.
Follow-up to #27. The WASM site is fully merged, but the GitHub Pages deploy failed on its first run (the #27 merge) at
actions/configure-pages@v5:This is the classic first-run chicken-and-egg: the action tried to read the Pages site before Pages was enabled with the GitHub Actions build type, got a 404, and aborted. Nothing was missing from #27 — the deploy just never retried (it only re-runs on a push to
deploy/wasm-web/**or the workflow file).Fix
Add
enablement: trueto theconfigure-pagesstep so it enables Pages via the API if it isn't already, making the workflow self-sufficient and idempotent:What happens on merge
Merging this touches the workflow path → re-triggers the deploy →
configure-pagesnow passes →deploy-pagespublishesdeploy/wasm-web/to https://liujonathan24.github.io/NetHackHarness/.(The Node-20 deprecation warnings in the failed log are non-fatal; the action versions used are already current.)
https://claude.ai/code/session_01D3HuJeFjkPti8RgmT88joG