Improve ad hoc hook warning about `required_executable`/`command` tracked by git

[KamilLelonek]

My .overcommit.yml looks like:

PrePush:
  RuboCop:
    enabled: true
    command: ['bundle', 'exec', 'rubocop']
    on_warn: fail

  RSpec:
    enabled: true
    command: ['bundle', 'exec', 'rspec']
    on_warn: fail

PostCheckout:
  BundleInstall:
    enabled: true
    on_warn: fail

And when I try to git push I get a message:

Hook must specify a `required_executable` or `command` that is tracked by git (i.e. is a path relative to the root of the repository) so that it can be signed

What should I do in such case?

[sds]

Hey @KamilLelonek,

There is no RuboCop pre-push hook available out of the box. You need to create one.

Since there is no RuboCop pre-push hook, Overcommit assumes you are trying to create an "ad hoc" hook—hooks which don't require a separate Ruby implementation file (RSpec is an example of a hook which has a separate Ruby implementation).

In order for Overcommit to provide security checks as outlined in the Security section, it requires ad hoc hooks to refer to scripts that are tracked by Git in your repository, which is why you're seeing the error message in question.

In this case I agree the error message could elaborate on this a bit, so I'll leave this open to track that update.

[sds]

As of 5a0a4ec you can specify arbitrary commands as ad hoc hooks. This should make creating hooks like this possible!