-
Notifications
You must be signed in to change notification settings - Fork 935
Treat warnings as error in doc generation #2097
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
base: master
Are you sure you want to change the base?
Conversation
🎉 All Contributor License Agreements have been signed. Ready to merge. |
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.
Pull Request Overview
This PR configures Sphinx documentation generation to treat warnings as errors by adding the -W
flag to the SPHINXOPTS
variable. This ensures that documentation builds fail when warnings are present, helping maintain documentation quality and catch issues early in the development process.
- Added the
-W
flag toSPHINXOPTS
to enable strict warning handling
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
This comment has been minimized.
This comment has been minimized.
d491557
to
60ff184
Compare
This comment has been minimized.
This comment has been minimized.
60ff184
to
2104da8
Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
docs/conf.py
Outdated
# further. For a list of options available for each theme, see the | ||
# documentation. | ||
html_theme_path = [sphinx_rtd_theme.get_html_theme_path()] | ||
# html_theme_path = [sphinx_rtd_theme.get_html_theme_path()] |
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.
I'm assuming the theme still loads from line 131 and this plus import becomes unnecessary. Did you double check the rendering is preserving the theme? If so I'd just delete rather than comment these lines
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.
I built the documentation before and after the removal and compared both versions visually and using vimdiff. Only a minor difference was observed: the character used to represent links after section headers had changed. This is not a significant issue, so we can proceed with removing that part.
No description provided.