t7510: use $PWD instead of $(pwd) inside PATH
On Windows, $(pwd) will give us a Windows-style path like "D:/foo". Putting that into $PATH confuses anybody parsing that variable, since colon is a separator character in $PATH. Instead, we should use the Unix-style value we get from $PWD ("/d/foo"). This is similar to the cases fixed by 71dd50472d (t0021, t5615: use $PWD instead of $(pwd) in PATH-like shell variables, 2016-11-11). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Jul 25, 2025 at 01:13 UTC
c26ecaf069080c6f9f98925530394a5b4c53e325
1 file changed
+1
-1
t/t7510-signed-commit.sh
+1
-1
index 95d2ebe277..1201c85ba6 100755
--- a/t/t7510-signed-commit.sh
+++ b/t/t7510-signed-commit.sh
@@ -458,7 +458,7 @@ test_expect_success 'custom `gpg.program`' '
# `gpg.program` does not specify an absolute path, it should find a program in `$PATH`
test_config gpg.program "fake-gpg" &&
- env PATH="$(pwd):$PATH" \
+ env PATH="$PWD:$PATH" \
git commit -S --allow-empty -m signed-commit
'