From: jjengla@sandia.gov
To: git@vger.kernel.org
Cc: "Josh England" <jjengla@sandia.gov>
Subject: [PATCH] Add post-merge hook.
Date: Thu, 30 Aug 2007 16:40:17 -0600 [thread overview]
Message-ID: <11885136172952-git-send-email-jjengla@sandia.gov> (raw)
From: Josh England <jjengla@sandia.gov>
This adds a post-merge hook that will run after `git pull` operations
if enabled. The hook is passed no arguments and cannot affect the
outcome of a merge.
Signed-off-by: Josh England <jjengla@sandia.gov>
---
Documentation/hooks.txt | 8 ++++++++
git-merge.sh | 6 ++++++
2 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/Documentation/hooks.txt b/Documentation/hooks.txt
index c39edc5..841b37f 100644
--- a/Documentation/hooks.txt
+++ b/Documentation/hooks.txt
@@ -87,6 +87,14 @@ parameter, and is invoked after a commit is made.
This hook is meant primarily for notification, and cannot affect
the outcome of `git-commit`.
+post-merge
+-----------
+
+This hook is invoked by `git-merge`, which happens when a `git pull`
+is done on a local repository.
+
+The hook takes no parameters, and cannot affect the outcome of `git-merge`.
+
[[pre-receive]]
pre-receive
-----------
diff --git a/git-merge.sh b/git-merge.sh
index 3a01db0..0a77bfb 100755
--- a/git-merge.sh
+++ b/git-merge.sh
@@ -97,6 +97,12 @@ finish () {
fi
;;
esac
+
+ # Run a post-merge hook
+ if test -x "$GIT_DIR"/hooks/post-merge
+ then
+ "$GIT_DIR"/hooks/post-merge
+ fi
}
merge_name () {
--
1.5.3.rc7-dirty
next reply other threads:[~2007-08-30 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 22:40 jjengla [this message]
2007-08-30 23:07 ` [PATCH] Add post-merge hook Junio C Hamano
2007-09-04 16:25 ` Josh England
2007-09-04 17:25 ` Junio C Hamano
2007-09-04 19:36 ` Josh England
2007-09-04 20:03 ` Junio C Hamano
2007-09-04 20:32 ` Josh England
2007-09-04 20:52 ` Steven Grimm
2007-09-04 21:23 ` Josh England
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11885136172952-git-send-email-jjengla@sandia.gov \
--to=jjengla@sandia.gov \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).