Summary
GitHub Pages for this repo is configured to serve from master:/docs, but docs/ was deleted (commit c425dd8) and is now gitignored (.gitignore line 1: docs/*). As a result pages-build-deployment fails on every single push to the default branch.
An origin/gh-pages branch already exists, and the modern wads uv CI's epythet docs job publishes to gh-pages root — so the content is already being produced in the right place; only the Pages source setting is stale.
Why this is filed rather than fixed
Changing a repo's Pages configuration is a repo-settings change (maintainer decision), so it was deliberately held back during the 2026-07-30 rollout pass rather than applied unprompted. The failing pages-build-deployment runs on PR #3 are this pre-existing condition, not a regression from that PR.
Fix
gh api -X PUT repos/i2mint/unbox/pages -f 'source[branch]=gh-pages' -f 'source[path]=/'
Then confirm:
gh api repos/i2mint/unbox/pages --jq '.source'
gh run list --repo i2mint/unbox --workflow pages-build-deployment --limit 3
curl -sI https://i2mint.github.io/unbox/ | head -1
Note
This is the fleet-standard modern layout (gh-pages root, published by the CI docs job) versus the old master:/docs layout. Other repos in the ecosystem may have the same stale setting — worth spot-checking any repo whose pages-build-deployment is persistently red while its CI docs job is green.
Surfaced during the 2026-07-30 wave-0 rollout batch.
Summary
GitHub Pages for this repo is configured to serve from
master:/docs, butdocs/was deleted (commitc425dd8) and is now gitignored (.gitignoreline 1:docs/*). As a resultpages-build-deploymentfails on every single push to the default branch.An
origin/gh-pagesbranch already exists, and the modern wads uv CI'sepythetdocs job publishes togh-pagesroot — so the content is already being produced in the right place; only the Pages source setting is stale.Why this is filed rather than fixed
Changing a repo's Pages configuration is a repo-settings change (maintainer decision), so it was deliberately held back during the 2026-07-30 rollout pass rather than applied unprompted. The failing
pages-build-deploymentruns on PR #3 are this pre-existing condition, not a regression from that PR.Fix
Then confirm:
Note
This is the fleet-standard modern layout (gh-pages root, published by the CI docs job) versus the old master:/docs layout. Other repos in the ecosystem may have the same stale setting — worth spot-checking any repo whose
pages-build-deploymentis persistently red while its CI docs job is green.Surfaced during the 2026-07-30 wave-0 rollout batch.