Hey again, On Mon, Sep 21, 2020 at 07:15:09AM -0400, Ahmed Hassan wrote: > However, I want to see all the pylint issues to be shown within the PR > instead of another console.
You can do that by registering a "problem matcher" file with GitHub Actions, which defines a regex to parse the console output. Here's what I came up with: https://github.com/PyCQA/pylint/pull/2758#issuecomment-696059847 Example of it in use (though with a false-positive): https://github.com/qutebrowser/qutebrowser/pull/5317/files#diff-aae12401377bf852929e08604e560acdR143 Some more docs: https://github.com/actions/toolkit/blob/master/docs/problem-matchers.md > Also, I don't want to run pylint on the whole file, I want to run it > only on the code that was added. I don't think that's possible from pylint's side. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
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
