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

[PATCH] t6300: fix setup with GPGSSH but without GPG

From
René Scharfe <l.s.r@web.de>
Date
Jul 16, 2023, 08:17 UTC
Message-ID
<cbc22750-af93-9274-2ed4-6dfd356568e8@web.de>

In a test introduced by 26c9c03f0a (ref-filter: add new "signature" atom, 2023-06-04) the file named "file" is added by a setup step that requires GPG and modified by a second setup step that requires GPGSSH. Systems lacking the first prerequisite skip the initial setup step and then "git commit -a" in the second one doesn't find the modified file. Add it explicitly.

Signed-off-by: René Scharfe <l.s.r@web.de>
---
 t/t6300-for-each-ref.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
index 6e6ec852b5..1180c3254c 100755
--- a/t/t6300-for-each-ref.sh
+++ b/t/t6300-for-each-ref.sh
@@ -1584,7 +1584,8 @@ test_expect_success GPGSSH 'setup for signature atom using ssh' '
 	test_config user.signingkey "${GPGSSH_KEY_PRIMARY}" &&
 	echo "8" >file &&
 	test_tick &&
-	git commit -a -S -m "file: 8" &&
+	git add file &&
+	git commit -S -m "file: 8" &&
 	git tag eighth-signed-ssh
 '

--
2.41.0
Next: Christian Couder
Message 1 of 4 in “t6300: fix setup with GPGSSH but without GPG”
  1. t6300: fix setup with GPGSSH but without GPGRené Scharfe, Jul 16, 2023
  2. Christian CouderJul 17, 2023
  3. Junio C HamanoJul 17, 2023
  4. René ScharfeJul 17, 2023

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.