The first parameter to the post-update hook is the branch reference in full – for instance I see ‘refs/heads/master’ for a push to ‘origin master’. So an example hook script that just prints the branch modified is: #!/bin/sh branch=$(git rev-parse –symbolic –abbrev-ref $1) echo Update pushed to branch $branch exec git update-server-info To illustrate, when … Read more
If you need to execute a script after a git pull on the client side (your machine), then a there is no reliable solution. The post-merge client-side hook (mentioned here) won’t be triggered by every pull (for instance, not in a pull rebase, not in case of fast-forward merge) So an alias wrapping both commands … Read more
I would check to make sure that each step of the way, your script returns a non-zero exit code on failure. Check to see if your python3.1 foo.py –test returns a non-zero exit code if a test fails. Check to make sure your make test command returns a non-zero exit code. And finally, check that … Read more
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!
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
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
I figured out what was causing that: I had created my pre-commit hook in git core directory, but the git had created a pre-commit hook in project’s .git/hooks/ directory. I just removed it. It means running the command that @romin21 mentioned inside project’s root directory: rm -rf .git/hooks
For obvious reasons, GitHub won’t allow you to execute arbitrary code on their servers as part of Git hooks. The only hooking they allow is through their webhooks or the integrated third-party services. If you need to run some custom code, you will have to host that somewhere and set up a webhook to run … Read more
With git 2.9, you have a new option made for centralizing hooks: core.hooksPath See commit 867ad08, commit de0824e, commit bf7d977, commit 49fa52f (04 May 2016) by Ævar Arnfjörð Bjarmason (avar). (Merged by Junio C Hamano — gitster — in commit 6675f50, 17 May 2016) The git config documentation now includes: core.hooksPath By default Git will … Read more
(author of pre-commit here) the framework intentionally does not provide a way to auto-commit modifications. Here’s a few issues which have asked for such: pre-commit/pre-commit#806 pre-commit/pre-commit#747 A comment from one of those issues: pre-commit itself will never touch the staging area. These are good ways to silently break commits. In my mind this is one … Read more