Re: Gerrit Code-Style verification -- was ESC / Rome discussion ...

On Wed, Nov 1, 2017 at 8:44 AM, David Ostrovsky <d.ostrovsky@gmx.de> wrote:

> On Mon, Oct 30 08:35:36 UTC 2017, Miklos Vajna wrote:
>
> > On Fri, Oct 27, 2017 at 04:49:55PM +0200, Jan Holesovsky wrote:

[...]


> Many OSS projects in the wild enforce code styles. Some projects,
> even enforce multiple different code style checks for different
> languages and even different checks for a single language.
>
> One example is tensoflow:
> https://github.com/tensorflow/tensorflow/blob/c44f67a7ed5870fe8a1c0d625
> 7ce597ca2ef7564/tensorflow/tools/ci_build/ci_sanity.sh
> <https://github.com/tensorflow/tensorflow/blob/c44f67a7ed5870fe8a1c0d6257ce597ca2ef7564/tensorflow/tools/ci_build/ci_sanity.sh>
>
> is using:
>
> * pylint
> * pep8
> * buildifier (Bazel BUILD files)
> * clang_format_check

This may be of interest, https://coala.io/#/languages. It is umbrella tool
that covers over many different checkers and linters. It may ease
implementation effort, esp. for multi language project. Add this one tool,
the checkers you need, and it will run them for you and collate results.
There may be other tools such as coala, I haven't looked.

[...]

And no, I'm not volunteering to do the job.
>

Me neither
-- 
Jiri Daněk