Publish the built site to a pages branch for Ken's server to serve (#27)
CI / test (pull_request) Successful in 39s

Every push to main builds the static site (npm run build -> dist/) and force-pushes it as the only commit of
the `pages` branch. Ken's web server serves that branch (a git-sync sidecar or a pull on a timer): nothing
on his server needs a secret, since the repository is public, and the site updates within minutes of every
merge, data PRs included.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
This commit is contained in:
2026-11-19 16:36:08 +00:00
co-authored by Claude Opus 5.5
parent 0df6b8d473
commit 0ae29b5423
2 changed files with 39 additions and 2 deletions
+2 -2
View File
@@ -13,8 +13,8 @@ branch: main
# public, limited (only people signed in to this server) or private: who can open the links below
visibility: limited
# the published page, when it is hosted somewhere (GitHub Pages is paused while the GitHub account is suspended;
# the page is viewed locally or as a Claude artifact meanwhile)
# the published page: Ken's server serves the `pages` branch (.gitea/workflows/pages.yml). Set this to its address
# once it is up (then `python -m collection build`): the page's links and the dataset metadata use it.
site: null
# other copies of the repository (informational)