Adding support for locally-defined hooks - #226

weird, there's a pre-commit hook that should split this line, does this line change when pre-commit run --all-files ? (might be a side-effect of rebase?)

My bad, I hadn't install pre-commit properly on this repo ! Fixed

I'd just change these to raise NotImplementedError

I think you can explicitly include both of those exceptions:

with pytest.raises((jsonschema.exceptions.ValidationError, InvalidConfigError)):
    # ...

one last thing (sorry, didn't notice this on the first passes), is there a reason to raise this error? it should just work now that we're doing it at the repository right? (it's a bit silly I agree, but it should work just fine if the check is removed?)

Yes, but I prefer to be strict at this early stage of config parsing, instead of allowing weird anomalies later.
E.g. if one needs a list of all the local hooks and assume there can be only one entry for them in the config.
Better avoid ambiguity, don't you think ?

I feel that if it's not broken, why go through the extra trouble to exclude the case?

Also, since hooks run in the order they are defined, it might be desirable to run some hooks out-of-order. We currently don't forbid repeated repos at the moment so I see no reason to make local repos special in that regard.

Ok, this last argument convinced me. I'm going to remove the check.