.hgrc/hooks automatic hook directory

[anatoly techtonik]

On Sat, Jan 5, 2019 at 2:07 AM Marcin Kasperski
<Marcin.Kasperski at mekk.waw.pl> wrote:
>
> > For example, if I want to run script after every clone, it is
> > impossible to create this
> > script in `~/.hgrc/hook/post-clone` to make it executed automatically?
>
> In most cases I wanted things like that, I ended up converting hook (or
> hooks pack) into extension. Which is easy to install and makes
> installation one-time affair. And extension can easily execute on many
> paths without specific config.

Rewriting this as an extension won't help with drop-in installation. The
installation procedure is exactly the same as with hooks, it is not easier,
and therefore doesn't solve the problem.

Hooks are common interface for every version control system. Environment
variables are also used for Continuous Integration systems, so I won't have
to completely rewrite the logic for non-hg projects. I also remember that the
only stable API for Mercurial is CLI. Did that change?

-- 
anatoly t.