Repository navigation
Add Writer CI and protected manual Pages deployments - #10
Merged
Merged
Conversation
callumalpass
force-pushed
the
ci/writer-ci
branch
from
October 2, 2026 23:29
3b56b22 to
f2bafe3
Compare
callumalpass
force-pushed
the
ci/writer-ci
branch
from
October 2, 2026 23:34
f2bafe3 to
aa3c377
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.
Writer had no CI: PRs merged on local checks, and production deployed from a laptop (
pnpm deploy:prod).main: install,pnpm check(typecheck, tests, manifest), production and staging builds, and the Chromium suites (browser-test.mjsandbrowser-reliability-test.mjsagainst the?democollection).workflow_dispatchwith a staging or production target, modelled on Reader'sdeploy-reader.yml. It reusesscripts/deploy-pages.mjs, runs frommainonly and is environment-protected.Settings needed before the deploy workflow works (detailed in
docs/development.md):writer-stagingandwriter-production, restricted tomain, with required reviewers on production.CLOUDFLARE_API_TOKEN(Cloudflare Pages: Edit) andCLOUDFLARE_ACCOUNT_IDin both environments.main.Validation: actionlint passes. Locally: checks, both builds and all 20 reliability scenarios pass. One adoption scenario flaked once and passed on rerun; no assertions were weakened.