git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Add post-merge hook.

From
Jjjengla@sandia.gov <jjengla@sandia.gov>
Date
Aug 30, 2007, 22:40 UTC
Message-ID
<11885136172952-git-send-email-jjengla@sandia.gov>
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: Junio C Hamano
Message 1 of 9 in “Add post-merge hook.”
  1. Add post-merge hook.jjengla@sandia.gov, Aug 30, 2007
  2. Junio C HamanoAug 30, 2007
  3. Josh EnglandSep 4, 2007
  4. Junio C HamanoSep 4, 2007
  5. Josh EnglandSep 4, 2007
  6. Junio C HamanoSep 4, 2007
  7. Josh EnglandSep 4, 2007
  8. Steven GrimmSep 4, 2007
  9. Josh EnglandSep 4, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.