Closed tsevan closed 9 years ago
@tsevan you can convert your tool into pre-commit plugin, for an example check: https://github.com/pre-commit-plugins/pre-commit-php
@mpapis Okay, I published there: https://github.com/tsevan/pre-commit-closure-linter. I'm also going to add a configuration opportunity soon.
@jish 1) we could get it to https://github.com/pre-commit-plugins/ 2) if not do we keep list of all the external plugins? maybe a wiki?
"1) we could get it to https://github.com/pre-commit-plugins/"
sure.
"2) if not do we keep list of all the external plugins? maybe a wiki?"
Yea, we should probably list plugins whether they live in pre-commit-plugins
or not... I added a very simple page here https://github.com/jish/pre-commit/wiki/Plugins we can obviously iterate on it and clean it up.
@tsevan I've created https://github.com/pre-commit-plugins/pre-commit-closure-linter and added you as a collaborator. We can move the plugin there if you like, or you can leave it under your name and delete the repo under pre-commit-plugins
. Whatever works best ;)
I suggest connecting
pre-commit
andclosure_linter
. We use their guide in our project for JS codestyle, and it would be nice to do that automatically.This implementation requires external install of
closure_linter
(which is available in ubuntu in theuniverse
repo f.e.). I put a note about this fact in README.Thanks.