Skip to content

ci: add mkdocs --strict docs build as a required check#215

Merged
lesnik512 merged 1 commit into
mainfrom
ci-docs-strict-build
Jun 14, 2026
Merged

ci: add mkdocs --strict docs build as a required check#215
lesnik512 merged 1 commit into
mainfrom
ci-docs-strict-build

Conversation

@lesnik512

Copy link
Copy Markdown
Member

What

Adds docs-build verification to CI so documentation breakage fails the build.

  • New just docs-build recipe: uvx --with-requirements docs/requirements.txt mkdocs build --strict (mirrors docs-deploy).
  • New docs job in the reusable .github/workflows/_checks.yml, so it runs on every PR/push (via ci.yml) and in the weekly scheduled dep-check (via scheduled.yml).

Why

CI ran only lint + pytest and never built the docs. The site-wide admonition-rendering regression fixed in #214 (and any future broken link / missing nav entry / bad mkdocs config) would pass CI undetected. --strict turns those into build failures.

Verification

  • just docs-build passes locally (exit 0).
  • This PR's own CI exercises the new docs job.

🤖 Generated with Claude Code

Adds a 'docs-build' just recipe (uvx + docs/requirements.txt, mkdocs build
--strict) and a 'docs' job to the reusable _checks workflow, so broken
links, missing nav entries, and config errors fail CI on every PR. CI
previously only ran lint + pytest and never built the docs, so the recent
admonition-extension regression (#214) would not have been caught.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 force-pushed the ci-docs-strict-build branch from cd11907 to 4d248ba Compare June 14, 2026 07:22
@lesnik512 lesnik512 merged commit 4ff7c76 into main Jun 14, 2026
7 checks passed
@lesnik512 lesnik512 deleted the ci-docs-strict-build branch June 14, 2026 07:23
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