From: Junio C Hamano <gitster@pobox.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>,
Karthik Nayak <karthik.188@gmail.com>
Subject: Re: [RFC PATCH 1/3] t0009: add tests to cover more error reporting scenarios
Date: Thu, 24 Sep 2026 15:08:39 -0700 [thread overview]
Message-ID: <xmqqjyoaz4ig.fsf@gitster.g> (raw)
In-Reply-To: <20260924120502.2642141-2-kaartic.sivaraam@gmail.com> (Kaartic Sivaraam's message of "Thu, 24 Sep 2026 17:32:19 +0530")
Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:
> Introduce few more tests to t0009 to cover error reporting scenarios
> when --git-dir is used.
>
> Signed-off-by: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
> ---
> t/t0009-git-dir-validation.sh | 36 +++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
>
> diff --git a/t/t0009-git-dir-validation.sh b/t/t0009-git-dir-validation.sh
> index 4cba478e50..244dc07c0e 100755
> --- a/t/t0009-git-dir-validation.sh
> +++ b/t/t0009-git-dir-validation.sh
> @@ -74,4 +74,40 @@ test_expect_success 'setup: .git as an empty directory is ignored' '
> )
> '
>
> +test_expect_success 'setup: custom git directory with missing HEAD is rejected' '
> + test_when_finished "rm -rf parent/empty-dir" &&
> + mkdir -p parent/empty-dir &&
> + (
> + test_must_fail git --git-dir parent/empty-dir rev-parse --is-bare-repository 2>stderr &&
> + test_grep "not a git repository" stderr
> + )
> +'
Why subshell?
> +
> +test_expect_success 'setup: custom git directory with HEAD as a symlink outside refs/ is rejected' '
> + test_when_finished "rm -rf parent/head-as-link-to-garbage" &&
> + mkdir -p parent/head-as-link-to-garbage &&
> + (
> + cd parent/head-as-link-to-garbage &&
> + git init --bare real-repo &&
> + touch garbage &&
> + rm real-repo/HEAD &&
> + ln -s ../garbage real-repo/HEAD &&
> + test_must_fail git --git-dir real-repo rev-parse --is-bare-repository 2>stderr &&
> + test_grep "not a git repository" stderr
> + )
> +'
> +
> +test_expect_success 'setup: custom git directory with invalid GIT_OBJECT_DIRECTORY configuration is rejected' '
> + test_when_finished "rm -rf parent/invalid-git-object-directory-config" &&
> + mkdir -p parent/invalid-git-object-directory-config &&
> + (
> + cd parent/invalid-git-object-directory-config &&
> + git init --bare real-repo &&
> + test_must_fail env GIT_OBJECT_DIRECTORY="$(pwd)/does-not-exist" \
> + git --git-dir real-repo rev-parse --is-bare-repository 2>stderr &&
> + test_grep "not a git repository" stderr
> + )
> +'
> +
> +
> test_done
next prev parent reply other threads:[~2026-09-24 22:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 12:02 [RFC PATCH 0/3] Improve error reporting to mention "why" a directory is not a repository Kaartic Sivaraam
2026-09-24 12:02 ` [RFC PATCH 1/3] t0009: add tests to cover more error reporting scenarios Kaartic Sivaraam
2026-09-24 22:08 ` Junio C Hamano [this message]
2026-09-25 13:46 ` Kaartic Sivaraam
2026-09-24 12:02 ` [RFC PATCH 2/3] setup: introduce new helper 'is_git_directory_verbose' Kaartic Sivaraam
2026-09-24 22:11 ` Junio C Hamano
2026-09-25 17:51 ` Kaartic Sivaraam
2026-09-24 12:02 ` [RFC PATCH 3/3] setup: communicate why a directory is not a valid git directory Kaartic Sivaraam
2026-09-24 22:16 ` Junio C Hamano
2026-09-25 14:33 ` Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 0/4] Improve error reporting to mention "why" a directory is not a repository Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 1/4] setup: normalize an if-else to follow our convention Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 2/4] t0009: add tests to cover more error reporting scenarios Kaartic Sivaraam
2026-09-29 10:25 ` [RFC PATCH v2 3/4] setup: introduce new helper 'is_git_directory_verbose' Kaartic Sivaraam
2026-09-30 16:03 ` Patrick Steinhardt
2026-10-05 12:14 ` Kaartic Sivaraam
2026-09-30 18:32 ` Junio C Hamano
2026-09-29 10:25 ` [RFC PATCH v2 4/4] setup: communicate why a directory is not a valid git directory Kaartic Sivaraam
2026-09-30 16:03 ` Patrick Steinhardt
2026-10-05 12:29 ` Kaartic Sivaraam
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=xmqqjyoaz4ig.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.