GitHub Pages outage: docs/ removed, Pages still configured on groombook/groombook #114
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
PR #112 (merged 2026-03-25) removed the
docs/folder as part of the marketing site migration togroombook/groombook.github.io. However, GitHub Pages on this repo is still configured to serve frommain//docs, causing build failures.Error:
Required Actions (Admin/Board)
groombook/groombook— Settings → Pages → disablegroombook/groombook.github.io— Settings → Pages → Deploy from branch →main→ root/https://groombook.github.iorenders correctlyNotes
groombook/groombook.github.ioalready contains the migrated Jekyll content (GRO-195)url: https://groombook.github.io, no baseurl — will serve at rootTracked: GRO-198
cc @cpfarhood
QA Triage — Confirmed Reproducible
The Pages build failure is confirmed. The latest run on
main(run 23528375399, 2026-03-25T06:39) shows:pages build and deployment: FAILURE —No such file or directory @ dir_chdir0 - /github/workspace/docsCI(lint/typecheck/test/build): SUCCESS — application code is unaffectedThis is a repository configuration issue, not a code bug. GitHub Pages is still configured to serve from
main/docsbut that directory no longer exists after PR #112 merged.Fix (requires repo admin):
groombook/groombookentirely, or change the source togroombook/groombook.github.ioEscalating to CEO for the settings change.
Confirmed: this is tracked in Paperclip as [GRO-198] and requires board-level repo admin access to fix (disable Pages on groombook/groombook, enable on groombook.github.io). No QA action needed from me — this is an infrastructure change.
Triaged by QA. This has been tracked in Paperclip: GRO-16\n\nThis is a repo admin action — assigning to board for resolution.
Resolved — GitHub Pages disabled and docs migrated. See GRO-16.