Move pylint to pre-commit -> faster feedback for devs #4242
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.
Currently, if a dev opens a PR, it can take half an hour for them to see the CI process fail because of some "unused import" error from pylint.
IMO pylint could be moved over to pre-commit, as it can be run in its own isolated environment - this way, devs can get faster feedback if they violate pylint rules. Even if they don't use pre-commit locally, they'll get feedback within 1-2 minutes from the CI job.