CI/CD: More informative linter output #12353
Merged
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.
Motivation
First time or sporadic contributors may have missed installing the
pre-commit
hook. In this situation, un-formatted code may be accidentally pushed. In such case, the output of the linter is not very informative:The goal is to make the output of the linter more informative, so the actual cause of the problem is clearer which could result in a better developer experience.
Changes
Adding the
--diff
option to thepython -m ruff format --check .
command.So the output would show the difference between the current file and how the formatted file would look like. For instance, the previous example would look like this:
If the output is too verbose,
| top 10
could be added to trim the output while still being informative.Unfortunately
ruff
doesn't seem to have a less verbose output as other linters may have,--diff
seems the only option available to get feedback of the problems found.