On Mon, Sep 21, 2020 at 07:15:09AM -0400, Ahmed Hassan wrote: > @Florian: Pylint itself is perfectly fine. However, I want to see all the > pylint issues to be shown within the PR instead of another console. Also, I > don't want to run pylint on the whole file, I want to run it only on the code > that was added.
diff-cover is a nice tool that can show missing code coverage or new lint issues for a git branch. Basically it computes the diff and then filters reports produced by other tools (coverage, pylint) to show only those that affect changed lines. Check it out: https://github.com/Bachmann1234/diff_cover#quality-coverage Marius Gedminas -- Favorite MS-DOS error message: "Drive C: not ready, close door."
signature.asc
Description: PGP signature
_______________________________________________ code-quality mailing list -- code-quality@python.org To unsubscribe send an email to code-quality-le...@python.org https://mail.python.org/mailman3/lists/code-quality.python.org/ Member address: arch...@mail-archive.com
