]> git.madduck.net Git - code/vcsh.git/blob - doc/hooks

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

Release v1.20140507
[code/vcsh.git] / doc / hooks
1 Available hooks are:
2
3 * pre-clone
4 * post-clone
5 * post-clone-retired
6         Use this if you need to operate on different git repositories after cloning.
7         This hook can be useful if your configuration needs some remote
8         repositories, but you do not want to include it into your vcsh
9         repository. For instance, if you use vim plugins manager (vundle,
10         NeoBundle), zsh configuration frameworks (oh-my-zsh, prezto), etc.
11 * pre-command
12 * post-command
13 * pre-enter
14 * post-enter
15 * pre-init
16 * post-init
17 * pre-merge
18         Use this hook to detect and handle merge conflicts before vcsh's native code
19         finds and errors on them. This is useful for allowing clones on top of existing
20         files.
21 * post-merge
22         Use this hook to finish handling any merge conflicts found in the pre-merge hook.
23 * pre-pull
24 * post-pull
25 * pre-push
26 * post-push
27 * pre-run
28 * post-run
29 * pre-upgrade
30 * post-upgrade
31
32 If you write any interesting or useful hooks, please send them upstream
33 so they can be included in an examples section.