Treat warnings as errors in doc building action #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is this PR
Why is this PR needed?
On issue #252, @lochhh pointed out that
sphinx-build
returns a successful exit code (0) even if it encountered errors.This can be quite annoying: in practice it means we need to remember to manually check the logs of the action (or locally), to confirm that there were no errors, even if the action shows a pass.
The simplest workaround seems to add the flags
-W --keep-going
so thatsphinx-build
runs to completion, treats warnings as errors, and returns a non-zero exit code if there are errors or warnings.What does this PR do?
Adds the flags
-W --keep-going
to thesphinx-build
in the doc building workflow file.References
In
movement
we build the docs in CI usingmake
, and have a PR to add the-W --keep-going
to the makefile:How has this PR been tested?
I have checked that the syntax of the
sphinx-build
command works locally as expected. I am not sure how to test this further.Is this a breaking change?
I think no.
Does this PR require an update to the documentation?
AFAIK this is not documented beyond the workflow file itself.
Checklist: