So I just found a command that I think i can use to detect the “merge_head” git rev-parse -q –verify MERGE_HEAD If rev-parse returns a hash that means we are currently in a merge state. I can use that to bypass this logic. But will wait for some better advice from more experienced individuals.
The core.hooksPath support is new in Git version 2.9, having been put in with commit 867ad08a2610526edb5723804723d371136fc643. If your Git version is not at least 2.9.0, setting a hooks-path variable will have no effect at all.
If you are looking for something robust and easy to maintain, I’d encourage you to develop a solution around GitHub Webhooks. Yes it will require you to deploy a HTTP server, say a Node.js server, and it will require a small amount of development (your requirements are fairly specific), but I think it will pay-off … Read more
You missed a hook. The one you want is commit-msg: This hook is invoked by git commit, and can be bypassed with –no-verify option. It takes a single parameter, the name of the file that holds the proposed commit log message. Exiting with non-zero status causes the git commit to abort. So for example: #!/bin/sh … Read more
After further investigation and testing, here is a working solution: create file .git/hooks/hook-chain as follows #!/bin/bash # # author: orefalo hookname=`basename $0` FILE=`mktemp` trap ‘rm -f $FILE’ EXIT cat – > $FILE for hook in $GIT_DIR/hooks/$hookname.* do if test -x “$hook”; then # echo $hook cat $FILE | $hook “$@” status=$? if test $status -ne … Read more
The term “right answer” is a bit ambiguous in this case. I actually think that “all revs reachable from newrev but nowhere else” is completely correct. This is true even if there was a merge – in that case, you should see the commits unique to the new ref, and the merge commit, but not … Read more
You can use the –watchAll=false parameter. So for example you can create another script like this: “scripts”: { “test:nowatch”: “react-scripts test –watchAll=false”, } And then run “pre-commit”: [ “precommit-msg”, “lint”, “test:nowatch” ],
You can’t: the push command figures out which commits to push before invoking the hook, and pushes that if the hook exits 0. I see three options: Exit nonzero, telling the user “push rejected because I added a commit” Exit zero, telling the user “push went through but you’ll need to push again because I … 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
You can add a post-receive hook to the ~/bar.com.git repo for this. To do this add to the ~/bar.com.git/hooks/ directory an executable file post-receive with the content: #!/bin/sh unset $(git rev-parse –local-env-vars) cd ~/bar.com git pull Make sure the post-receive file has the executable bits(e.g. 755). Now whenever something is pushed to the ~/bar.com.git repo, … Read more