sapling/eden/hooks
Michael Bolin 625ec8100c Create an .hg/branch file by default.
Summary:
Some tools/script may be blindly assuming the presence of this file,
so rather than fight them, just create it.

Reviewed By: simpkins

Differential Revision: D8020274

fbshipit-source-id: 712e3bf31a0aefe27cc20f5361a0edb59c7deb9f
2018-05-15 21:52:15 -07:00
..
hg Create an .hg/branch file by default. 2018-05-15 21:52:15 -07:00
generate-hooks-dir Update script because --into was changed to --out. 2017-01-09 16:02:04 -08:00
README.md Update the hg/post-clone hook to write the .hg/dirstate file. 2017-10-27 13:35:26 -07:00

Eden hooks

When Eden is deployed, the output of generate-hooks-dir should be installed in /etc/eden/hooks.

By default, Eden will look in /etc/eden/hooks for hooks. This can be overridden by specifying hooks in the [repository] section of an ~/.edenrc.

Note that hooks may require additional configuration. Hook authors should encourage users to specify such configuration in ~/.edenrc. This can be read from the hook via eden config.

The following files will be recognized in the hooks directory for the appropriate event:

post-clone

This will be run after eden clone. If the <repo_type> is .hg, the script is responsible for creating the .hg directory in the root of the Eden mount. It will receive the following arguments:

/etc/eden/hooks/hg/post-clone <repo_type> <eden_checkout> <repo>
  • <repo_type> is hg or git
  • <eden_checkout> is the path to the mounted Eden checkout.
  • <repo> is the path to the original Mercurial repository.
  • <hash> is the hex id of the initial commit