3 # Copyright (c) 2007 Andy Parkins
5 # An example hook script to mail out commit update information. This hook
6 # sends emails listing new revisions to the repository introduced by the
7 # change being reported. The rule is that (for branch updates) each commit
8 # will appear on one email and one email only.
10 # This hook is stored in the contrib/hooks directory. Your distribution
11 # will have put this somewhere standard. You should make this script
12 # executable then link to it in the repository you would like to use it in.
13 # For example, on debian the hook is stored in
14 # /usr/share/doc/git-core/contrib/hooks/post-receive-email:
16 # chmod a+x post-receive-email
17 # cd /path/to/your/repository.git
18 # ln -sf /usr/share/doc/git-core/contrib/hooks/post-receive-email hooks/post-receive
20 # This hook script assumes it is enabled on the central repository of a
21 # project, with all users pushing only to it and not between each other. It
22 # will still work if you don't operate in that style, but it would become
23 # possible for the email to be from someone other than the person doing the
29 # This is the list that all pushes will go to; leave it blank to not send
30 # emails for every ref update.
32 # This is the list that all pushes of annotated tags will go to. Leave it
33 # blank to default to the mailinglist field. The announce emails lists
34 # the short log summary of the changes since the last annotated tag.
35 # hooks.envelopesender
36 # If set then the -f option is passed to sendmail to allow the envelope
37 # sender address to be set
39 # All emails have their subjects prefixed with this prefix, or "[SCM]"
40 # if emailprefix is unset, to aid filtering
44 # All emails include the headers "X-Git-Refname", "X-Git-Oldrev",
45 # "X-Git-Newrev", and "X-Git-Reftype" to enable fine tuned filtering and
46 # give information for debugging.
49 # ---------------------------- Functions
52 # Top level email generation function. This decides what type of update
53 # this is and calls the appropriate body-generation routine after outputting
56 # Note this function doesn't actually generate any email output, that is
57 # taken care of by the functions it calls:
58 # - generate_email_header
59 # - generate_create_XXXX_email
60 # - generate_update_XXXX_email
61 # - generate_delete_XXXX_email
62 # - generate_email_footer
67 oldrev=$(git rev-parse $1)
68 newrev=$(git rev-parse $2)
75 if expr "$oldrev" : '0*$' >/dev/null
79 if expr "$newrev" : '0*$' >/dev/null
87 # --- Get the revision types
88 newrev_type=$(git cat-file -t $newrev 2> /dev/null)
89 oldrev_type=$(git cat-file -t "$oldrev" 2> /dev/null)
90 case "$change_type" in
93 rev_type="$newrev_type"
97 rev_type="$oldrev_type"
101 # The revision type tells us what type the commit is, combined with
102 # the location of the ref we can decide between
107 case "$refname","$rev_type" in
111 short_refname=${refname##refs/tags/}
115 refname_type="annotated tag"
116 short_refname=${refname##refs/tags/}
118 if [ -n "$announcerecipients" ]; then
119 recipients="$announcerecipients"
124 refname_type="branch"
125 short_refname=${refname##refs/heads/}
127 refs/remotes/*,commit)
129 refname_type="tracking branch"
130 short_refname=${refname##refs/remotes/}
131 echo >&2 "*** Push-update of tracking branch, $refname"
132 echo >&2 "*** - no email generated."
136 # Anything else (is there anything else?)
137 echo >&2 "*** Unknown type of update to $refname ($rev_type)"
138 echo >&2 "*** - no email generated"
143 # Check if we've got anyone to send to
144 if [ -z "$recipients" ]; then
145 case "$refname_type" in
147 config_name="hooks.announcelist"
150 config_name="hooks.mailinglist"
153 echo >&2 "*** $config_name is not set so no email will be sent"
154 echo >&2 "*** for $refname update $oldrev->$newrev"
158 # The email subject will contain the best description of the ref
159 # that we can build from the parameters
162 # Call the correct body generation function
164 case "$refname_type" in
165 "tracking branch"|branch)
175 revs=$(list_${change_type}_branch_revs 2>/dev/null)
177 if [ "$change_type" != "update" ]
179 set_update_branch_subject
181 generate_email_header
182 generate_${change_type}_branch_email
183 generate_email_footer
193 # set_update_branch_subject will return false if the
194 # commit is boring (no change). Then we don't even
196 set_update_branch_subject || continue
198 generate_email_header
199 print_change_info $newrev
200 summarize_branch_revs
201 generate_email_footer
208 generate_email_header
209 generate_${change_type}_${fn_name}_email
210 generate_email_footer
218 describe=$(git describe --abbrev=4 $1 2>/dev/null || git rev-parse --short $1)
219 describe=$(echo "$describe" | sed -e 's/-/./g;s/^v//;')
222 generate_email_header()
224 # --- Email (all stdout will be the email)
226 print_change_type="${change_type}d "
227 case "$change_type" in
233 print_reftype="$refname_type "
234 case "$refname_type" in
240 case "$short_refname" in
245 print_refname="$short_refname "
250 Subject: ${emailprefix}$print_reftype$print_refname$print_change_type$detail
251 X-Git-Refname: $refname
252 X-Git-Reftype: $refname_type
253 X-Git-Newrev: $newrev
258 generate_email_footer()
268 # --------------- Branches
271 # Called for the creation of a branch
273 generate_create_branch_email()
275 # This is a new branch and so oldrev is not valid
276 echo " at $newrev ($newrev_type)"
280 generic_list_branch_revs()
284 # We want to list all revs that are reachable now, but
286 # All revs that were reachable before are git rev-parse --branches.
287 # However, this includes $refname. The naive | grep -v $branchtip
288 # will not work, because another branch might already have been on
289 # $branchtip. In this case we shouldn't list any rev.
290 # As git rev-parse --branches might list a given rev multiple times
291 # if there are multiple branches at this rev, we simply drop this
292 # $branchtip rev once, and pass all subsequent ones through.
294 branchtip=$(git rev-parse $refname)
296 git rev-parse --not --branches | sed -e "1,/$branchtip/{/$branchtip/d;}" |
297 git rev-list --reverse --stdin $range
300 list_create_branch_revs()
302 generic_list_branch_revs $newrev
306 # Called for the change of a pre-existing branch
308 generate_update_branch_email()
310 # XXX only valid for fast forwards
312 # List all the revisions from baserev to newrev in a kind of
313 # "table-of-contents"; note this list can include revisions that
314 # have already had notification emails and is present to show the
315 # full detail of the change from rolling back the old revision to
316 # the base revision and then forward to the new revision
317 for rev in $(git rev-list $oldrev..$newrev)
319 revtype=$(git cat-file -t "$rev")
320 echo " via $rev ($revtype)"
323 echo " from $oldrev ($oldrev_type)"
329 skip_diff_tree_parent()
339 set_update_branch_subject()
343 detail=$(git show -s --pretty=format:%s $newrev 2>/dev/null)
345 [ -n "$(git diff-tree -r --name-only --cc $oldrev${oldrev:+..}$newrev 2>/dev/null |
346 skip_diff_tree_parent)" ]
349 list_update_branch_revs()
351 generic_list_branch_revs $oldrev..$newrev
354 summarize_branch_revs()
356 echo "Summary of changes:"
357 git diff-tree --stat --summary --find-copies-harder $oldrev${oldrev:+..}$newrev | skip_diff_tree_parent
359 if [ -n "$gitweburl" ]
362 echo "$gitweburl/$reponame/commitdiff/$oldrev${oldrev:+..}$newrev"
370 git rev-list -n 1 --pretty $1
374 # Called for the deletion of a branch
376 generate_delete_branch_email()
381 git show -s --pretty=oneline $oldrev
385 # --------------- Annotated tags
388 # Called for the creation of an annotated tag
390 generate_create_atag_email()
392 echo " at $newrev ($newrev_type)"
398 # Called for the update of an annotated tag (this is probably a rare event
399 # and may not even be allowed)
401 generate_update_atag_email()
403 echo " to $newrev ($newrev_type)"
404 echo " from $oldrev (which is now obsolete)"
410 # Called when an annotated tag is created or changed
412 generate_atag_email()
414 # Use git for-each-ref to pull out the individual fields from the
416 eval $(git for-each-ref --shell --format='
417 tagobject=%(*objectname)
418 tagtype=%(*objecttype)
420 tagged=%(taggerdate)' $refname
423 echo " tagging $tagobject ($tagtype)"
427 # If the tagged object is a commit, then we assume this is a
428 # release, and so we calculate which tag this tag is
430 prevtag=$(git describe --abbrev=0 $newrev^ 2>/dev/null)
432 if [ -n "$prevtag" ]; then
433 echo " replaces $prevtag"
437 echo " length $(git cat-file -s $tagobject) bytes"
440 echo " tagged by $tagger"
446 # Show the content of the tag message; this might contain a change
447 # log or release notes so is worth displaying.
448 git cat-file tag $newrev | sed -e '1,/^$/d'
453 # Only commit tags make sense to have rev-list operations
455 if [ -n "$prevtag" ]; then
456 # Show changes since the previous release
457 git rev-list --no-merges --pretty=short "$prevtag..$newrev" | git shortlog
459 # No previous tag, show all the changes since time
460 # began, but only summarize due to the possibly large size.
461 git rev-list --no-merges --pretty=short $newrev | git shortlog -s
465 # XXX: Is there anything useful we can do for non-commit
474 # Called for the deletion of an annotated tag
476 generate_delete_atag_email()
481 git show -s --pretty=oneline $oldrev
485 # --------------- General references
488 # Called when any other type of reference is created (most likely a
491 generate_create_general_email()
493 echo " at $newrev ($newrev_type)"
495 generate_general_email
499 # Called when any other type of reference is updated (most likely a
502 generate_update_general_email()
504 echo " to $newrev ($newrev_type)"
507 generate_general_email
511 # Called for creation or update of any other type of reference
513 generate_general_email()
515 # Unannotated tags are more about marking a point than releasing a
516 # version; therefore we don't do the shortlog summary that we do for
517 # annotated tags above - we simply show that the point has been
518 # marked, and print the log message for the marked point for
521 # Note this section also catches any other reference type (although
522 # there aren't any) and deals with them in the same way.
525 if [ "$newrev_type" = "commit" ]; then
527 git show --no-color --root -s --pretty=medium $newrev
530 # What can we do here? The tag marks an object that is not
531 # a commit, so there is no log for us to display. It's
532 # probably not wise to output git cat-file as it could be a
533 # binary blob. We'll just say how big it is
534 echo "$newrev is a $newrev_type, and is $(git cat-file -s $newrev) bytes long."
539 # Called for the deletion of any other type of reference
541 generate_delete_general_email()
546 git show -s --pretty=oneline $oldrev
552 if [ -n "$envelopesender" ]; then
553 /usr/sbin/sendmail -t -f "$envelopesender"
555 /usr/sbin/sendmail -t
559 # ---------------------------- main()
566 # Set GIT_DIR either from the working directory, or from the environment
568 GIT_DIR=$(git rev-parse --git-dir 2>/dev/null)
569 if [ -z "$GIT_DIR" ]; then
570 echo >&2 "fatal: post-receive: GIT_DIR not set"
574 projectdesc=$(sed -ne '1p' "$GIT_DIR/description")
575 # Check if the description is unchanged from it's default, and shorten it to
576 # a more manageable length if it is
577 if expr "$projectdesc" : "Unnamed repository.*$" >/dev/null
579 projectdesc="UNNAMED PROJECT"
582 recipients=$(git config hooks.mailinglist)
583 announcerecipients=$(git config hooks.announcelist)
584 envelopesender=$(git config hooks.envelopesender)
585 emailprefix=$(git config hooks.emailprefix || echo '[SCM] ')
586 gitweburl=$(git config hooks.gitweburl)
587 reponame=$(git config hooks.reponame || basename $(realpath $GIT_DIR))
590 # Allow dual mode: run from the command line just like the update hook, or
591 # if no arguments are given then run as a hook script
592 if [ -n "$1" -a -n "$2" -a -n "$3" ]; then
593 # Output to the terminal in command line mode - if someone wanted to
594 # resend an email; they could redirect the output to sendmail
597 generate_email $2 $3 $1
599 while read oldrev newrev refname
602 generate_email $oldrev $newrev $refname