-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check mkdocs build strict in CI #1360
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good one to check, I left some suggestions. Let me know what you think!
021e363
to
aec8823
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
renamed the old python-ci-docs.yml to python-release-docs.yml
.github/workflows/python-ci-docs.yml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will now run on every PR when there's a change in mkdocs/docs/
9d24bc4
to
13e558c
Compare
verified that CI breaks with bad doc changes https://github.com/apache/iceberg-python/actions/runs/11963956201/job/33355402732?pr=1360 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kevinjqliu for fixing this, this looks great!
13e558c
to
7a83695
Compare
* add ci to release docs * run mkdocs in ci * use 3.12
* add ci to release docs * run mkdocs in ci * use 3.12
* add ci to release docs * run mkdocs in ci * use 3.12
* add ci to release docs * run mkdocs in ci * use 3.12
This PR adds a new GitHub Action to run
mkdocs build --strict
for every PR.python-ci-docs.yml
was previously used to release doc changes, it's copied over and renamed topython-release-docs.yml
.python-ci-docs.yml
now runsmkdocs build --strict
for every PR.When releasing docs, the
python-ci-docs.yml
GitHub Action uses--strict
. This action is only triggered during the release process, which requires an ad-hoc fix, see #1334.iceberg-python/.github/workflows/python-ci-docs.yml
Line 42 in 7a83695
Lets make sure this is checked in new PRs