On Sun, Sep 27, 2015 at 2:20 AM, Ricordisamoa <ricordisamoa(a)openmailbox.org> wrote: :) Indeed! Thank you Legoktm, this is very useful and fits very well in our efforts to improve our code review practices. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

If you're intrigued by all the code checking automation available, Extension:BoilerPlate [1] implements both the `npm test` and `composer test` entry points, and people have updated it to run jshint, jscs, banana-checker, jsonlint, php-parallel-lint, and now PHP CodeSniffer. Its README [2] explains how to get rolling. So if you start a new extension from BoilerPlate or copy over its files, your extension or skin benefits from the same code checks. Then you can copy its Continuous Integration configuration [3] so that Jenkins run these tests on your extension or skin on each commit pushed to gerrit.wikimedia.org. [1] https://www.mediawiki.org/wiki/Extension:BoilerPlate [2] https://gerrit.wikimedia.org/r/#/c/237058/4/README.md [3] https://gerrit.wikimedia.org/r/#/c/226680/ On Sat, Sep 26, 2015 at 4:28 PM, Legoktm <legoktm.wikipedia(a)gmail.com> wrote: -- =S Page WMF Tech writer