t7003: ensure filter-branch prunes reflogs with the reftable backend

In t7003 we conditionally check whether the reflog for branches pruned by git-filter-branch(1) get deleted based on whether or not we use the "files" backend. Same as with the preceding commit, this condition was added because in its initial iteration the "reftable" backend did not delete reflogs when their corresponding ref was deleted. Since then, the backend has been aligned to behave the same as the "files" backend though, which makes this check unnecessary. Remove it. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Patrick Steinhardt committed Feb 15, 2024 at 09:25 UTC 5918f30b65020dd87c59c3144a7237eb8cb78a69
1 file changed +1 -4
t/t7003-filter-branch.sh
+1 -4
@@ -396,10 +396,7 @@ test_expect_success '--prune-empty is able to prune entire branch' '
396 git branch prune-entire B &&
397 git filter-branch -f --prune-empty --index-filter "git update-index --remove A.t B.t" prune-entire &&
398 test_must_fail git rev-parse refs/heads/prune-entire &&
399 - if test_have_prereq REFFILES
400 - then
401 - test_must_fail git reflog exists refs/heads/prune-entire
402 - fi
399 + test_must_fail git reflog exists refs/heads/prune-entire
400 '
401
402 test_expect_success '--remap-to-ancestor with filename filters' '