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

[PATCH 1/2] merge: don't run post-hook logic on --no-verify

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Feb 18, 2022, 20:43 UTC
Message-ID
<patch-1.2-9b5144daee6-20220218T203834Z-avarab@gmail.com>
In-Reply-To
<cover-0.2-00000000000-20220218T203834Z-avarab@gmail.com>

Fix a minor bug introduced in bc40ce4de61 (merge: --no-verify to bypass pre-merge-commit hook, 2019-08-07), when that change made the --no-verify option bypass the "pre-merge-commit" hook it didn't update the corresponding find_hook() (later hook_exists()) condition.

As can be seen in the preceding commit in 6098817fd7f (git-merge: honor pre-merge-commit hook, 2019-08-07) the two should go hand in hand. There's no point in invoking discard_cache() here if the hook couldn't have possibly updated the index.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
 builtin/merge.c | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/builtin/merge.c b/builtin/merge.c
index 133831d42fd..fab553e3bc4 100644
--- a/builtin/merge.c
+++ b/builtin/merge.c
@@ -845,15 +845,18 @@ static void prepare_to_commit(struct commit_list *remoteheads)
 	struct strbuf msg = STRBUF_INIT;
 	const char *index_file = get_index_file();
 
-	if (!no_verify && run_commit_hook(0 < option_edit, index_file, "pre-merge-commit", NULL))
-		abort_commit(remoteheads, NULL);
-	/*
-	 * Re-read the index as pre-merge-commit hook could have updated it,
-	 * and write it out as a tree.  We must do this before we invoke
-	 * the editor and after we invoke run_status above.
-	 */
-	if (hook_exists("pre-merge-commit"))
-		discard_cache();
+	if (!no_verify) {
+		if (run_commit_hook(0 < option_edit, index_file,
+				    "pre-merge-commit", NULL))
+			abort_commit(remoteheads, NULL);
+		/*
+		 * Re-read the index as pre-merge-commit hook could have updated it,
+		 * and write it out as a tree.  We must do this before we invoke
+		 * the editor and after we invoke run_status above.
+		 */
+		if (hook_exists("pre-merge-commit"))
+			discard_cache();
+	}
 	read_cache_from(index_file);
 	strbuf_addbuf(&msg, &merge_msg);
 	if (squash)
-- 
2.35.1.1031.g277d4562d2e
Previous: Ævar Arnfjörð BjarmasonNext: Junio C Hamano
Message 2 of 12 in “hooks: fix a race in hook execution”
  1. 0/2 hooks: fix a race in hook executionÆvar Arnfjörð Bjarmason, Feb 18, 2022
  2. 1/2 merge: don't run post-hook logic on --no-verifyÆvar Arnfjörð Bjarmason, Feb 18, 2022
  3. Junio C HamanoFeb 18, 2022
  4. 2/2 hooks: fix a TOCTOU in "did we run a hook?" heuristicÆvar Arnfjörð Bjarmason, Feb 18, 2022
  5. Junio C HamanoFeb 19, 2022
  6. Ævar Arnfjörð BjarmasonFeb 19, 2022
  7. Taylor BlauFeb 19, 2022
  8. Ævar Arnfjörð BjarmasonFeb 19, 2022
  9. 0/2 hooks: fix a race in hook executionÆvar Arnfjörð Bjarmason, Mar 7, 2022
  10. 1/2 merge: don't run post-hook logic on --no-verifyÆvar Arnfjörð Bjarmason, Mar 7, 2022
  11. 2/2 hooks: fix an obscure TOCTOU "did we just run a hook?" raceÆvar Arnfjörð Bjarmason, Mar 7, 2022
  12. Jonathan TanMar 21, 2022

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.