Don't run the linter ecosystem check on PRs that only touch red-knot crates #15687
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.
Summary
At some point we'll hopefully setup a
mypy_primer
-like check for red-knot. Until that point, however, comments like #15683 (comment) just cause noise and distraction through additional notifications, and it's a waste of our CI minutes.Test Plan
I used https://codepen.io/mrmlnc/pen/OXQjMe to check that the glob patterns listed here will match a path like
crates/ruff_linter/foo.rs
but will not matchcrates/red_knot/foo.rs
orcrates/red_knot_python_semantic/foo.rs
. https://codepen.io/mrmlnc/pen/OXQjMe is linked to from the README of https://github.com/tj-actions/changed-files/tree/v45/ as a tool you can use to test glob patterns passed as inputs to thechanged-files
GitHub action.