http://benjamin-meyer.blogspot.com/2008/10/git-hooks.html Files in the .git/hooks directory are not part of the repository and so they are not tracked. A workaround is to have a git_hooks directory at the top of your repository like done in Arora and symlink .git/hooks to git_hooks whenever you clone. This way the hooks will be part of the project, under … Read more
A git hook is a script placed in a special location of your repository, that location is: .git/hooks The script can be any kind that you can execute in your environment i.e. bash, python, ruby etc. The hook that is executed after a checkout is post-checkout. From the docs: …The hook is given three parameters… … Read more
Tags are refs like any other (like commit). If tags are pushed to a repo with a post-receive hook, that hook will be called and will list all updated refs, that is both old and new values of all the refs in addition to their names (on its standard input). See this server post-receive email … Read more
I don’t think so, as hooks are not cloned. May be if that hook script is itself versioned, and then link to (symbolic link) in the clone servers (provided their OS support that link feature). Or maybe if the hooks are part of a git template directory used for creating the clones (that would only … Read more
From the git-init man page (also works with git-clone if you are cloning an existing repo instead of creating a new one from scratch): –template=<template_directory> Provide the directory from which templates will be used. The default template directory is /usr/share/git-core/templates. When specified, <template_directory> is used as the source of the template files rather than the … Read more
Since git add was also not working for me in a pre commit, I followed mark’s idea of using a .commit file and splitting the process into pre- and post-commit. Here is some code that should be easy to understand In the pre-commit: Touch a file .commit or something. (be sure to add this to … Read more
Another solution to this problem is to have a wrapper for git push that executes .git/hooks/pre-push and .git/hooks/post-push scripts before and after the git push call. A possible wrapper could look like this: #!/bin/sh GIT_DIR_=”$(git rev-parse –git-dir)” BRANCH=”$(git rev-parse –symbolic –abbrev-ref $(git symbolic-ref HEAD))” PRE_PUSH=”$GIT_DIR_/hooks/pre-push” POST_PUSH=”$GIT_DIR_/hooks/post-push” test -x “$PRE_PUSH” && exec “$PRE_PUSH” “$BRANCH” “$@” git … Read more
Another, more modern way to do this is with git-multimail, as suggested by Chords below. This is how you did it in 2009. You could add something like this to your post-receive hook in $GITDIR/hooks, or use the script in the contrib directory of the source (Available here)
ok, one way to do this is to use the clone –template option. Specify the location where the client side hooks will be stored as value to the –template switch. The hooks are copied to the clone, and the post-checkout hook is fired immediately!