Calling the test tag "Tag" will make for confusing reading later in
this series when making use of the "git push tag <name>"
feature. Let's call the tag testTag instead.

Changes code initially added in dbfeddb12e ("push: require force for
refs under refs/tags/", 2012-11-29).

Signed-off-by: Ævar Arnfjörð Bjarmason <ava...@gmail.com>
---
 t/t5516-fetch-push.sh | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
index bd8f23e430..2cbe459ee6 100755
--- a/t/t5516-fetch-push.sh
+++ b/t/t5516-fetch-push.sh
@@ -971,18 +971,18 @@ test_expect_success 'push requires --force to update 
lightweight tag' '
        mk_child testrepo child2 &&
        (
                cd child1 &&
-               git tag Tag &&
-               git push ../child2 Tag &&
-               git push ../child2 Tag &&
+               git tag testTag &&
+               git push ../child2 testTag &&
+               git push ../child2 testTag &&
                >file1 &&
                git add file1 &&
                git commit -m "file1" &&
-               git tag -f Tag &&
-               test_must_fail git push ../child2 Tag &&
-               git push --force ../child2 Tag &&
-               git tag -f Tag &&
-               test_must_fail git push ../child2 Tag HEAD~ &&
-               git push --force ../child2 Tag
+               git tag -f testTag &&
+               test_must_fail git push ../child2 testTag &&
+               git push --force ../child2 testTag &&
+               git tag -f testTag &&
+               test_must_fail git push ../child2 testTag HEAD~ &&
+               git push --force ../child2 testTag
        )
 '
 
-- 
2.18.0.345.g5c9ce644c3

Reply via email to