Repository navigation
ci: the site lives in site/ and deploys from a workflow - #5
Merged
Merged
Conversation
extramoose
force-pushed
the
ci/pages-from-workflow
branch
from
September 14, 2026 00:42
6085068 to
409e6f9
Compare
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
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.
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 sitesymlinks 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.