automation: add workflow to fail on warnings during docs build #3948
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
consideRatio
force-pushed
the
pr/fail-on-docs-warnings
branch
2 times, most recently
from
6adf419
to
b2183f0
Compare
consideRatio
force-pushed
the
pr/fail-on-docs-warnings
branch
from
b2183f0
to
1f71da0
Compare
consideRatio
force-pushed
the
pr/fail-on-docs-warnings
branch
from
1f71da0
to
78e0021
Compare
GeorgianaElena
approved these changes
Apr 16, 2024
|
Thank you @GeorgianaElena! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I saw we had many sphinx build warnings that I figured we shouldn't have, because they are typically very relevant and introduced as part of changes into docs. This workflow will ensure we don't introduce warnings.