GitHub actions output format about pylint HOT 10 CLOSED

If no one is working on this I can do it

from pylint.

I think trying if this works with a template would be nice. Then we can just document that in the documentation.

Once it works as template string, maybe it'd still be beneficial to have something like github available as key one can pass to the --output-format (or a similiar?) flag such that users won't have to add something like

pylint --msg-template='{msg_id}:{line:3d},{column}: {obj}: {msg}' # example from the docs

and can instead simply go ahead and run

pylint --output-format=github   # or a similar cli flag

without having to know the "internals" of how the messages are to be outputted in order to be GitHub-action-consumable? But maybe that's just me being too lazy as a user.

from pylint.

No I think that is fair. We have recently added a new json reporter. You can probably look at that PR to see what stuff you'd need to add for it to work.

I'm on mobile right now so can't easily link the PR myself, sorry!

from pylint.

I made a dummy test with my PR changes:

https://github.com/zoftko/balba/pull/2/files

Just wondering if we should mark all annotations as error? Or make some sort of mapping between pylint message types and github annotation types.

For example Pylint has fatal, error, warning, convention, refactor and information type messages. Github has notice, warning and error annotations.

from pylint.

Thank you for opening this issue, great suggestion !

from pylint.

So I was checking the code and it seems like this could be done with --msg-template, in fact some reporters are marked as deprecated and suggest using --msg-template directly instead. Would this be the same case?

from pylint.

I think trying if this works with a template would be nice. Then we can just document that in the documentation. You could start there?

from pylint.

I also like the shortcut. Lazy users are the best users 😄
Here's hopefuly a link to the code of json reporters (other exemples are available in this directory) : https://github.com/pylint-dev/pylint/blob/main/pylint%2Freporters%2Fjson_reporter.py

from pylint.

It looks really great. I think pylint fatal should break the build, error should be mapped to error, warning to warning and pylint convention and refactor to github's notice.

from pylint.

@crazybolillo Many thanks for the quick implementation and thanks to everyone involved in the PR ❤

from pylint.