Skip to content

ci: the site lives in site/ and deploys from a workflow - #5

Merged
extramoose merged 2 commits into
mainfrom
ci/pages-from-workflow
Sep 14, 2026
Merged

extramoose merged 2 commits into
mainfrom
ci/pages-from-workflow

Conversation

@extramoose

@extramoose extramoose commented Sep 14, 2026 •

Copy link
Copy Markdown
Owner

Two things Joe called out, one PR.

Library and site are separate now: site/ holds the two pages, the social card, llms.txt and the domain file; the repository root is the library. The pages still import ./index.js off disk, which the Pages workflow copies in at deploy time and npm run site symlinks locally, so the site only ever runs the reviewed source.

The site deploys from that workflow, not from a branch root. Branch-root Pages served every file in the repository as a public URL: /package.json and /e2e/tooltip.spec.js were both 200 on tooltip.hah.to. The workflow ships the six files and nothing else, SHA-pinned actions, and configure-pages switches the source to GitHub Actions on its first run.

Verified locally on the assembled site/: home, docs and the card page load, the tooltip mounts, zero console errors, zero failed requests. After merge: /package.json should be 404, both pages 200, custom domain and HTTPS unchanged.

@extramoose extramoose changed the title ci: deploy the site from a workflow, not the branch root ci: the site lives in site/ and deploys from a workflow Sep 14, 2026
@extramoose
extramoose force-pushed the ci/pages-from-workflow branch from 6085068 to 409e6f9 Compare September 14, 2026 00:42
@extramoose
extramoose merged commit 7e6837e into main Sep 14, 2026
1 check passed
@extramoose
extramoose deleted the ci/pages-from-workflow branch September 14, 2026 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant