Ensure sarif extra is included as part of doc build #1139
Merged
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
The doc build nowadays runs via the readthedocs.yaml file. So the requirements for building those docs need to include sarif in order to correctly build the sarif formatter doc. Fixes: PyCQA#1138 Signed-off-by: Eric Brown <eric_wade_brown@yahoo.com>
|
Here's a link to successful readthedocs test build on this PR: https://ericwbbandit.readthedocs.io/en/doc_sarif/formatters/sarif.html Notice the sarif page works now. |
sigmavirus24
approved these changes
May 10, 2024
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.
The doc build nowadays runs via the readthedocs.yaml file. So the requirements for building those docs need to include sarif in order to correctly build the sarif formatter doc.
Fixes: #1138