Skip to content

Conversation

@scott-huberty
Copy link

@scott-huberty scott-huberty commented Nov 20, 2025

Closes #852

  • Run mkdocs build --strict on PR's to main or pushes to main
  • Docs deploy now depends on build succeeding.
  • Bump actions/checkout to v5
  • Pin Python version in Docs CI to 3.12 (for consistency)

EDIT: Tested the new doc build job on my fork first, and its green!

- Run mkdocs build --strict on PR's to main or pushes to main
- Docs 'deploy' now depends on 'build' succeeding.
- Bump actions/checkout
- Pin Python version in Docs job to 3.12
Copy link
Collaborator

@DetachHead DetachHead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

- uses: actions/setup-python@v5
with:
python-version: 3.x
python-version: '3.12'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to avoid duplicating the version number and make it easier to update in the future, can we make this a variable at the top of the file

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this thread is just a reminder to myself to add this to the list of required checks in the repo settings before merging

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.

ci check for mkdocs

2 participants