Originally created by @verwilst on GitHub (May 11, 2016).
Instead of a simple --hook, it would be nice to have a --pre-hook and --post-hook, so we can do cleanups afterwards.
Originally created by @verwilst on GitHub (May 11, 2016).
Instead of a simple --hook, it would be nice to have a --pre-hook and --post-hook, so we can do cleanups afterwards.
With that I don't see any reason why to make this script more complicated with dozens of hook parameters for any case where a hook could be called.
@lukas2511 commented on GitHub (May 11, 2016):
The hook script gets called with a parameter which tells it what to do, see https://github.com/lukas2511/letsencrypt.sh/blob/master/docs/examples/hook.sh.example.
With that I don't see any reason why to make this script more complicated with dozens of hook parameters for any case where a hook could be called.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @verwilst on GitHub (May 11, 2016).
Instead of a simple --hook, it would be nice to have a --pre-hook and --post-hook, so we can do cleanups afterwards.
@lukas2511 commented on GitHub (May 11, 2016):
The hook script gets called with a parameter which tells it what to do, see https://github.com/lukas2511/letsencrypt.sh/blob/master/docs/examples/hook.sh.example.
With that I don't see any reason why to make this script more complicated with dozens of hook parameters for any case where a hook could be called.
@verwilst commented on GitHub (May 12, 2016):
Ok, let's store this in the brainfart section. :-) Doh!