Source hooks instead of calling them?

[RichiH]

That would allow hooks to be a lot more powerful. But if there's an exit() in a hook today...

Or introduce a new kind of hook that's sourced:

source-post-clone
post-clone

[lyda]

The downside is that it means hooks must be shell scripts.

Perhaps only do it if the file isn't executable?

Note, should probably not run/source files that end in ~ as that's a common backup file for things like emacs.

[alerque]

By default I think hooks should stick closely to the Git hook handling: They should be executable in order to even be considered, and they should just be left to do their thing. As @lyda noted this means hooks can be in any language the user wants to support, something I take advantage of quite a bit.

If the ability to affect the parent environment is really needed we could setup some way of indicating that a particular hook should be sourced or allow it's output to be evaled or something like that, but lets not go sourcing all hooks by default.

[alerque]

cf. #177 and #207