sapling/eden/hooks
Adam Simpkins fe2f2e4cc9 forcibly disable the fbsparse extension
Summary:
Now that some parts of sparse are being upstreamed to core mercurial,
Facebook's sparse implementation has internally been renamed to "fbsparse".
Make sure the sparse extension is disabled inside eden repositories under both
names.

Reviewed By: bolinfest

Differential Revision: D6322114

fbshipit-source-id: c62b2ce25cb92519f2df1d7df6d43e2b209751d3
2017-11-14 20:07:15 -08:00
..
hg forcibly disable the fbsparse extension 2017-11-14 20:07:15 -08: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