Re: [PATCH 1/2] pretty: add %(describe)
- From
René Scharfe. <l.s.r@web.de>
- Date
- Feb 28, 2021, 11:22 UTC
- Message-ID
- <b70e1b3a-dd5f-1fbc-22d5-e2bca4c00e79@web.de>
- In-Reply-To
- <87k0r7a4sr.fsf@evledraar.gmail.com>
Am 17.02.21 um 01:58 schrieb Ævar Arnfjörð Bjarmason:
Show 9 quoted lines
> > On Sun, Feb 14 2021, René Scharfe wrote: > >> +'%(describe)':: human-readable name, like linkgit:git-describe[1]; >> + empty string for undescribable commits > > In the case of undescribable we've got the subcommand exiting non-zero > and we ignore it. The right thing in this case given how the rest of > format arguments work, but maybe something to explicitly test for?
The test convers it, but we can surely make that easier to see.
-- >8 -- Subject: [PATCH] t4205: assert %(describe) test coverage
Document that the test is covering both describable and undescribable commits.
Suggested-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: René Scharfe <l.s.r@web.de> --- t/t4205-log-pretty-formats.sh | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/t/t4205-log-pretty-formats.sh b/t/t4205-log-pretty-formats.sh index b47a0bd9eb..cabdf7d57a 100755 --- a/t/t4205-log-pretty-formats.sh +++ b/t/t4205-log-pretty-formats.sh @@ -965,8 +965,17 @@ test_expect_success 'log --pretty=reference is colored appropriately' ' test_expect_success '%(describe) vs git describe' ' git log --format="%H" | while read hash do - echo "$hash $(git describe $hash)" + if desc=$(git describe $hash) + then + : >expect-contains-good + else + : >expect-contains-bad + fi && + echo "$hash $desc" done >expect && + test_path_exists expect-contains-good && + test_path_exists expect-contains-bad && + git log --format="%H %(describe)" >actual 2>err && test_cmp expect actual && test_must_be_empty err -- 2.30.1