Skip to content

Commit 912072d

Browse files
draenoggitster
authored andcommitted
t6300: test sort with multiple keys
Documentation of git-for-each-ref says that --sort=<key> option can be used multiple times, in which case the last key becomes the primary key. However this functionality was never checked in test suite and is currently broken. This commit adds appropriate test in preparation for fix. Signed-off-by: Kacper Kornet <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent d0f1ea6 commit 912072d

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

t/t6300-for-each-ref.sh

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -456,4 +456,14 @@ test_atom refs/tags/signed-long contents "subject line
456456
body contents
457457
$sig"
458458

459+
cat >expected <<\EOF
460+
408fe76d02a785a006c2e9c669b7be5589ede96d <[email protected]> refs/tags/master
461+
90b5ebede4899eda64893bc2a4c8f1d6fb6dfc40 <[email protected]> refs/tags/bogo
462+
EOF
463+
464+
test_expect_failure 'Verify sort with multiple keys' '
465+
git for-each-ref --format="%(objectname) %(taggeremail) %(refname)" --sort=objectname --sort=taggeremail \
466+
refs/tags/bogo refs/tags/master > actual &&
467+
test_cmp expected actual
468+
'
459469
test_done

0 commit comments

Comments
 (0)