git: empty arguments in post-receive hook

git bash githooks
takeshin picture takeshin · Sep 21, 2010 · Viewed 11.6k times · Source

I'm writing post-receive hook basing on the post-receive-email script from the contrib dir, but it seems that the oldrev and newrev arguments are empty.

The script looks like this:

#!/bin/bash

oldrev=$(git rev-parse $1)
newrev=$(git rev-parse $2)

The script runs on push, but all $1, $2, $oldrev and $newrev are empty. Should I configure something to get it running?

(The repository was created by gitolite if it does matter)

Answer

François picture François · Jan 26, 2011

I stumbled into this problem while setting up a continuous integration server. Since the arguments are not passed to post-receive via the command line, but are passed over STDIN, you have to use the read command to fetch them. Here is how I did it:

#!/bin/sh
read oldrev newrev refname
BRANCH=${refname#refs/heads/} 
curl --request POST "http://my.ci.server/hooks/build/myproject_$BRANCH"

Related questions

Post Commit Hook Not Running

My post commit hook is not running after git. I have verified that the hook does work if I just run it from the terminal. The code in the hook is: #!/bin/sh #.git/hooks/post-commit # An example hook script …

Read More
How to run bash script after git push

I wanted to know how to execute a bash script in the local repo after pushing to github. The bash script is located in the root of the folder. It can be moved around depending on where it is being …

Read More
Git post-receive hook not working

We're using git with a central repo (using Gitosis). I've created a post-receive hook to generate an email to the dev mailing list whenever changes are pushed to the central repo, and to generate documentation from the documentation folder in …

Read More