-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Report Sphinx build warnings in CI #2402
Comments
MartinThoma
pushed a commit
that referenced
this issue
Jan 17, 2024
This adds a code style check to avoid unexpectedly shipping docs/docstrings which cause issues. Options (the long names are only part of the upcoming 7.3 release), based upon https://www.sphinx-doc.org/en/master/man/sphinx-build.html: * `-n`: Report warnings for missing references. * `-W`: Turn warnings into errors and stop at first violation. * `--keep-going`: Improve `-W` by collecting all violations and only failing at the end. * `-T`: Display the full traceback on actual errors. * `-b html`: Build HTML pages. * `docs`: Source directory. * `build/sphinx/html`: Target directory. Fixes #2402
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sphinx build warnings in CI currently remain unnoticed.
We should have a look at how we can integrate them into CI and let warnings/violations fail the corresponding workflow to avoid having to re-check manually each time.
The text was updated successfully, but these errors were encountered: