-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Clean up warnings in doc build #5610
Comments
Just wanted to drop a note here that there are still many docs warnings https://readthedocs.org/api/v2/build/13290377.txt for example |
Fixes issues like: * duplicate function documentation * indentation in bullet list problem * unknown target name
There are a few warnings, such as:
see https://readthedocs.org/api/v2/build/13290827.txt In which toctree, should these .rst files be included? |
is this issue still open for work?? |
This issue is still open. Feel free to contribute @rajpratyush |
I opened #8432 and dask/distributed#5549 to address the remaining build warnings. And I've enabled the option to treat build warnings as errors in those PRs. |
Re-opening as I think we still have a few warnings emitted during our documentation build. We should close this issue once we've enabled the "elevate warnings to errors" setting |
I know this issue is pretty old now - is it still valid? Looks from building the docs locally like I don't get any errors? Is the "elevate warnings to errors" aspect still relevant? In terms of building locally, this could be achieved with 'make html "SPHINXOPTS=-W"', but I'm guessing there are parts of cicd etc that need to do this instead potentially? |
Right now our doc build has many warnings. This makes it hard to catch newly introduced errors in the doc build. Sphinx has an option to elevate warnings to errors.
In the details, I've included some warnings from a recent local build
The text was updated successfully, but these errors were encountered: