ci: add Build Test workflow as the required status check#34
Merged
JohnRDOrazio merged 1 commit intomainfrom May 2, 2026
Merged
ci: add Build Test workflow as the required status check#34JohnRDOrazio merged 1 commit intomainfrom
JohnRDOrazio merged 1 commit intomainfrom
Conversation
Mirrors the build half of deploy-docs.yml — pandoc setup, npm ci, build:html, build:pdf — running unconditionally on every PR and on push to main. This serves two purposes: 1. Catch lockfile drift, pandoc/lua filter errors, and pagedjs/Chrome PDF rendering failures before they reach a tag-triggered deploy, which is the only path that currently exercises these scripts. 2. Provide a stable required status check for branch protection on main, including on Dependabot PRs that don't touch markdown (and so don't trigger the path-filtered Markdown Lint workflow). With a required check in place, 'gh pr merge --auto' in the dependabot auto-merge workflow has something to wait on instead of failing with 'Pull request Protected branch rules not configured'. WordPress upload, translation, and GitHub release steps are not exercised — they require live external services and run only on tag. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds
.github/workflows/build-test.yml— a CI workflow that runs the build half ofdeploy-docs.yml(pandoc setup,npm ci,build:html,build:pdf) on every PR and on push tomain. Catches the failure modes that currently only surface at deploy time:npm cifails)build:htmlfails)build:pdffails)The deploy-only steps — WordPress REST upload, translation worker, GitHub release — aren't exercised here; they need live external services and only run on tag.
Why this instead of running Lint Markdown on every PR
Lint Markdown is path-filtered to
**/*.mdfor good reason: it's irrelevant to PRs that don't touch markdown (e.g. Dependabot bumping a workflow SHA). Removing its path filter would have given us the required-check anchor for branch protection but at the cost of a useless 30-second job on every Dependabot PR. A build test is more meaningful: it actually validates that the PR doesn't break whatmainis supposed to ship.Follow-up after merge
Once this lands and runs once on a PR (so the check name
Build governance docsis registered in the API), enable branch protection onmain:Build governance docsstatus check to passWith that in place, the dependabot auto-merge workflow's
gh pr merge --auto --mergewill reliably have a check to wait on, fixing the residual race seen on PR #28.Test plan
mainper above--autofinds the required check)