DEV: avoid linting failures when running linting after documentation has been built - #32740
Merged
Merged
Conversation
Signed-off-by: Iason Krommydas <[email protected]>
Member
Author
|
Arghhh forgot to do skip actions again....... |
Member
Author
|
Should I add this folder to gitignore as well? |
Member
Seems like it, other generated doc files are there. |
Signed-off-by: Iason Krommydas <[email protected]>
Member
Author
Done |
Member
|
Thanks Iason. |
Riaz1729
pushed a commit
to Riaz1729/numpy
that referenced
this pull request
Sep 23, 2026
…has been built (numpy#32740) Signed-off-by: Iason Krommydas <[email protected]>
This file contains hidden or 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
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.
PR summary
Closes #32714
Linting these files causes thousands of linting failures when running spin lint after having ran spin docs.
Just add them exclude list for everyone.
AI Disclosure
No AI