Thanks Thomas, I will try that. That's my next option.

@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.

On Mon, Sep 21, 2020 at 6:47 AM Florian Bruhin <me@the-compiler.org> wrote:
Hey,

On Fri, Sep 18, 2020 at 05:55:29PM -0400, Ahmed Hassan wrote:
> Does anyone know an open source tool that checks PR before merge for code
> quality? I'm looking for something similar to code climate or codacy. I
> don't want to hook a Jenkins job that makes the usability of Pylint harder.

What do you mean with "makes the usability of Pylint harder" exactly?

The usual way is to run pylint via e.g. GitHub Actions or Travis CI,
usually also using something like tox or pre-commit.

https://docs.github.com/en/actions/guides/building-and-testing-python#running-tests-with-tox
https://tox.readthedocs.io/

Florian

--
me@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/


--

Ahmed Hassan

Engineering

Ahassan@RapidSOS.com


This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.