Skip to content

ci(docs): manual, main-only docs deploy on demand - #488

Open
JasonVranek wants to merge 1 commit into
mainfrom
docs/deploy-workflow
Open

ci(docs): manual, main-only docs deploy on demand#488
JasonVranek wants to merge 1 commit into
mainfrom
docs/deploy-workflow

Conversation

@JasonVranek

Copy link
Copy Markdown
Collaborator

Replace the abandoned stable-branch deploy (frozen at v0.9.3) with a Pages deploy that publishes the docs on the main branch.

The deploy is manual (workflow_dispatch), not push-triggered which has caused issues in the past.

test-docs runs the build on any PR that touches the docs or their linked inputs, so breakage is caught before merge.

Replace the abandoned `stable`-branch deploy (frozen at v0.9.3) with a
manual (`workflow_dispatch`) GitHub Pages deploy.

Publishing is restricted to `main` by two independent layers: the
`github-pages` environment's deployment-branch policy (set to `main` only),
and a guard step that fails the run if dispatched from any other ref. So
"only what's reviewed and merged to main is published" holds even though
workflow_dispatch's branch picker technically offers other branches.

Manual (not push-triggered) so publishing is a deliberate act and a failed
run can be re-fired without a new commit if the runner is unavailable.

test-docs runs the build on any PR touching docs or their linked inputs
(filter covers `config.example.toml`, drops `api/**` — the API spec is
fetched client-side at runtime, not built in).
@JasonVranek
JasonVranek requested a review from a team August 11, 2026 23:38
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