From: "Mansi Singh via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Mansi Singh <mansimaanu8627@gmail.com>,
Mansi Singh <mansimaanu8627@gmail.com>
Subject: [PATCH v2] t7605: use test_path_is_file instead of test -f
Date: Tue, 10 Mar 2026 22:50:22 +0000 [thread overview]
Message-ID: <pull.2067.v2.git.1773183022175.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2067.git.1773120813628.gitgitgadget@gmail.com>
From: Mansi Singh <mansimaanu8627@gmail.com>
Replace old-style 'test -f' path checks with the modern
test_path_is_file helper in the merge_c1_to_c2_cmds block.
The helper provides clearer failure messages and is the
established convention in Git's test suite.
Signed-off-by: Mansi Singh <mansimaanu8627@gmail.com>
---
t7605: use test_path_is_file instead of test -f
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2067%2FMansiSingh17%2Ffix-t7605-test-path-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2067/MansiSingh17/fix-t7605-test-path-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/2067
Range-diff vs v1:
1: 8753a5d919 ! 1: 388d8d7118 t7605: use test_path_is_file instead of test -f
@@
## Metadata ##
-Author: Mansi <mansimaanu8627@gmail.com>
+Author: Mansi Singh <mansimaanu8627@gmail.com>
## Commit message ##
t7605: use test_path_is_file instead of test -f
@@ Commit message
The helper provides clearer failure messages and is the
established convention in Git's test suite.
- These instances were found using:
- grep -rn "test -[efd]" t/ --include="*.sh"
-
- Signed-off-by: Mansi <mansimaanu8627@gmail.com>
+ Signed-off-by: Mansi Singh <mansimaanu8627@gmail.com>
## t/t7605-merge-resolve.sh ##
@@ t/t7605-merge-resolve.sh: merge_c1_to_c2_cmds='
t/t7605-merge-resolve.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/t/t7605-merge-resolve.sh b/t/t7605-merge-resolve.sh
index 5d56c38546..44de97a480 100755
--- a/t/t7605-merge-resolve.sh
+++ b/t/t7605-merge-resolve.sh
@@ -34,9 +34,9 @@ merge_c1_to_c2_cmds='
test "$(git rev-parse c1)" = "$(git rev-parse HEAD^1)" &&
test "$(git rev-parse c2)" = "$(git rev-parse HEAD^2)" &&
git diff --exit-code &&
- test -f c0.c &&
- test -f c1.c &&
- test -f c2.c &&
+ test_path_is_file c0.c &&
+ test_path_is_file c1.c &&
+ test_path_is_file c2.c &&
test 3 = $(git ls-tree -r HEAD | wc -l) &&
test 3 = $(git ls-files | wc -l)
'
base-commit: d181b9354cf85b44455ce3ca9e6af0b9559e0ae2
--
gitgitgadget
next prev parent reply other threads:[~2026-03-10 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 5:33 [PATCH] t7605: use test_path_is_file instead of test -f Mansi Singh via GitGitGadget
2026-03-10 13:30 ` Junio C Hamano
2026-03-10 22:50 ` Mansi Singh via GitGitGadget [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-24 5:34 Mansi Singh via GitGitGadget
2026-02-26 0:57 ` [PATCH v2] " Mansi Singh via GitGitGadget
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=pull.2067.v2.git.1773183022175.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=mansimaanu8627@gmail.com \
/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