repo: add paths.git_dir to 'git repo info' by jayesh0104 · Pull Request #2242 · git/git

jayesh0104 · 2026-03-17T14:23:52Z

Teach git repo info a new key, paths.git_dir, which reports the repository’s gitdir path (equivalent to git rev-parse --git-dir).

Documentation and tests are included.

Tests:

make test T=t1900-repo-info.sh

cc: Karthik Nayak karthik.188@gmail.com
cc: Justin Tobler jltobler@gmail.com
cc: Ayush Chandekar ayu.chandekar@gmail.com
cc: Siddharth Asthana siddharthasthana31@gmail.com
cc: Tian Yuchen a3205153416@gmail.com

gitgitgadget-git · 2026-03-17T14:24:31Z

Welcome to GitGitGadget

Hi @jayesh0104, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests.

Please make sure that either:

Your Pull Request has a good description, if it consists of multiple commits, as it will be used as cover letter.
Your Pull Request description is empty, if it consists of a single commit, as the commit message should be descriptive enough by itself.

You can CC potential reviewers by adding a footer to the PR description with the following syntax:

CC: Revi Ewer <revi.ewer@example.com>, Ill Takalook <ill.takalook@example.net>

NOTE: DO NOT copy/paste your CC list from a previous GGG PR's description,
because it will result in a malformed CC list on the mailing list. See
example.

Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:

the lines should not exceed 76 columns,
the first line should be like a header and typically start with a prefix like "tests:" or "revisions:" to state which subsystem the change is about, and
the commit messages' body should be describing the "why?" of the change.
Finally, the commit messages should end in a Signed-off-by: line matching the commits' author.

It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code.

Contributing the patches

Before you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form /allow. A good way to find other contributors is to locate recent pull requests where someone has been /allowed:

Search: is:pr is:open "/allow"

Both the person who commented /allow and the PR author are able to /allow you.

An alternative is the channel #git-devel on the Libera Chat IRC network:

<newcontributor> I've just created my first PR, could someone please /allow me? https://github.com/gitgitgadget/git/pull/12345
<veteran> newcontributor: it is done
<newcontributor> thanks!

Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment /submit.

If you want to see what email(s) would be sent for a /submit request, add a PR comment /preview to have the email(s) sent to you. You must have a public GitHub email address for this. Note that any reviewers CC'd via the list in the PR description will not actually be sent emails.

After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail).

If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the (raw) link), then import it into your mail program. If you use GMail, you can do this via:

curl -g --user "<EMailAddress>:<Password>" \
    --url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt

To iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description):

Changes since v1:
- Fixed a typo in the commit message (found by ...)
- Added a code comment to ... as suggested by ...
...

To send a new iteration, just add another PR comment with the contents: /submit.

Need help?

New contributors who want advice are encouraged to join git-mentoring@googlegroups.com, where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join.

You may also be able to find help in real time in the developer IRC channel, #git-devel on Libera Chat. Remember that IRC does not support offline messaging, so if you send someone a private message and log out, they cannot respond to you. The scrollback of #git-devel is archived, though.

gitgitgadget-git · 2026-03-17T14:24:32Z

Invalid author email in e2accc1: "86013121+jayesh0104@users.noreply.github.com"

gitgitgadget-git · 2026-03-17T14:24:33Z

Invalid author email in 6963ae0: "86013121+jayesh0104@users.noreply.github.com"

gitgitgadget-git · 2026-03-17T14:24:34Z

Invalid author email in f07605e: "86013121+jayesh0104@users.noreply.github.com"

gitgitgadget-git · 2026-03-17T15:42:42Z

There are issues in commit f80434e:
Add get_paths_git_dir function to repo.c

Commit checks stopped - the message is too short
Commit not signed off

gitgitgadget-git · 2026-03-17T15:42:42Z

There is an issue in commit d373fd9:
Document 'paths.git_dir' key in git-repo

Commit not signed off

gitgitgadget-git · 2026-03-17T15:42:43Z

There is an issue in commit c71df10:
Add test for paths.git_dir consistency

Commit not signed off

leuasseurfarrelds247-arch

064fe7f3312418007dea2b49a19844a9ee378f49

jayesh0104 · 2026-03-17T16:27:49Z

/preview

gitgitgadget-git · 2026-03-17T16:28:25Z

Error: User jayesh0104 is not yet permitted to use GitGitGadget

dscho · 2026-03-17T16:31:54Z

cc: Karthik Nayak karthik.188@gmail.com cc: Justin Tobler jltobler@gmail.com cc: Ayush Chandekar ayu.chandekar@gmail.com cc: Siddharth Asthana siddharthasthana31@gmail.com

Please read the instructions carefully. This Cc: list goes into the PR description, not just a random PR comment anywhere in the PR.

jayesh0104 · 2026-03-17T16:33:48Z

cc: Karthik Nayak karthik.188@gmail.com cc: Justin Tobler jltobler@gmail.com cc: Ayush Chandekar ayu.chandekar@gmail.com cc: Siddharth Asthana siddharthasthana31@gmail.com

Please read the instructions carefully. This Cc: list goes into the PR description, not just a random PR comment anywhere in the PR.

Thanks for the clarification , got it. I’ve updated the PR description to include the Cc: list in the correct place instead of adding it as a separate comment. Please let me know if anything else needs adjustment.

dscho · 2026-03-17T16:34:42Z

@jayesh0104 also, if you want to avoid being yelled at by the Git maintainer, you will want to reconsider those commit messages. Have a look around via git log, and you will see that one-liners or two-liners, especially ones without that Signed-off-by: trailer, will never ever make it into Git proper.

You definitly will want to follow the guidance in https://github.blog/2022-06-30-write-better-commits-build-better-projects/ to improve it, in particular with a strong focus on this part:

	What you’re doing	Why you’re doing it
High-level (strategic)	Intent (what does this accomplish?)	Context (why does the code do what it does now?)
Low-level (tactical)	Implementation (what did you do to accomplish your goal?)	Justification (why is this change being made?)

dscho · 2026-03-17T16:36:37Z

Finally, the changes of those three commits seem to belong into a single commit. You will want to squash them into a single one as described here.

Introduce a new repo info key `paths.git_dir` to expose the repository's gitdir path, equivalent to `git rev-parse --git-dir`. This improves consistency and allows tools to retrieve the gitdir path without invoking external commands. The implementation adds support in repo.c and integrates it into the repo info reporting mechanism. Documentation is updated to describe the new key, and tests are added to verify that the value matches the output of `git rev-parse --git-dir`. Signed-off-by: jayesh0104 <jayeshdaga99@gmail.com>

jayesh0104 · 2026-03-17T16:43:55Z

Finally, the changes of those three commits seem to belong into a single commit. You will want to squash them into a single one as described here.

Thanks for pointing this out, I understand the issue now. I’ll rework the commit messages to follow Git’s conventions, including adding proper structure and the required Signed-off-by: trailer.

I’ll also review git log examples and update the messages to clearly explain both the what and the why, as suggested. I’ll push an updated version shortly.

dscho · 2026-03-17T16:52:05Z

/allow

gitgitgadget-git · 2026-03-17T16:53:48Z

Error: User jayesh0104 is not yet permitted to use GitGitGadget

jayesh0104 · 2026-03-17T16:54:13Z

/submit

gitgitgadget-git · 2026-03-17T16:54:28Z

User jayesh0104 is now allowed to use GitGitGadget.

WARNING: jayesh0104 has no public email address set on GitHub; GitGitGadget needs an email address to Cc: you on your contribution, so that you receive any feedback on the Git mailing list. Go to https://github.com/settings/profile to make your preferred email public to let GitGitGadget know which email address to use.

gitgitgadget-git · 2026-03-17T16:55:33Z

Submitted as pull.2242.git.git.1773766519857.gitgitgadget@gmail.com

To fetch this version into FETCH_HEAD:

git fetch https://github.com/gitgitgadget/git/ pr-git-2242/jayesh0104/master-v1

To fetch this version to local tag pr-git-2242/jayesh0104/master-v1:

git fetch --no-tags https://github.com/gitgitgadget/git/ tag pr-git-2242/jayesh0104/master-v1

dscho · 2026-03-17T16:56:07Z

@jayesh0104 you will want to learn some patience, otherwise this will not be the best of experiences you'll get in your life. If you /preview before the /allow automation was allowed to finish, and then proceed to /submit after receiving an error message that the /preview failed, you will not enjoy the waiting times while reviewers are too busy to look at your patch.

gitgitgadget-git · 2026-04-07T06:41:58Z

Karthik Nayak wrote on the Git mailing list (how to reply to this email):

"Jayesh Daga via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: jayesh0104 <jayeshdaga99@gmail.com>
>
> Introduce a new repo info key `paths.git_dir` to expose the
> repository's gitdir path, equivalent to `git rev-parse --git-dir`.
>
> This improves consistency and allows tools to retrieve the gitdir
> path without invoking external commands.
>
> The implementation adds support in repo.c and integrates it into
> the repo info reporting mechanism. Documentation is updated to
> describe the new key, and tests are added to verify that the value
> matches the output of `git rev-parse --git-dir`.
>

Hello Jayesh,

Seeing from the people CC'd I'm assuming that you're interested in
applying for the GSoC.

As such, we encourage GSoC contributors to work on micro-projects as
listed on our GSoC website and also to read the guidelines we've laid
out [1] [2].

I would also mention that we do not recommend getting started on a
project, unless you're selected.

Now specifically for this project, there is still no decision made about
using relative paths vs absolute paths, I've highlighted this in one of
the candidates proposals [3]. I would suggest getting involved in that
discussion and coming to a conclusion before starting work on it.

[1]: https://git.github.io/General-Microproject-Information/
[2]: https://git.github.io/General-Application-Information/
[3]: https://lore.kernel.org/git/CAOLa=ZTtNSZ904v0-SN16jAis7gK4=MVj1g_5CGdbmaBopeZkg@mail.gmail.com/#t

Regards,
Karthik

[snip]

gitgitgadget-git · 2026-04-07T06:46:01Z

Tian Yuchen wrote on the Git mailing list (how to reply to this email):

Hi Jayesh,

On 3/18/26 00:55, Jayesh Daga via GitGitGadget wrote:
> From: jayesh0104 <jayeshdaga99@gmail.com>
> > Introduce a new repo info key `paths.git_dir` to expose the
> repository's gitdir path, equivalent to `git rev-parse --git-dir`.

Here you promise in the commit message that paths.git_dir and git rev-parse --git-dir are equivalent...

> > This improves consistency and allows tools to retrieve the gitdir
> path without invoking external commands.
> > The implementation adds support in repo.c and integrates it into
> the repo info reporting mechanism. Documentation is updated to
> describe the new key, and tests are added to verify that the value
> matches the output of `git rev-parse --git-dir`.
> > Signed-off-by: jayesh0104 <jayeshdaga99@gmail.com>
> ---
>      repo: add paths.git_dir to 'git repo info'
>      >      Teach git repo info a new key, paths.git_dir, which reports the
>      repository’s gitdir path (equivalent to git rev-parse --git-dir).
>      >      Documentation and tests are included.
>      >      Tests:
>      >       * make test T=t1900-repo-info.sh
> > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2242%2Fjayesh0104%2Fmaster-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2242/jayesh0104/master-v1
> Pull-Request: https://github.com/git/git/pull/2242
> >   Documentation/git-repo.adoc |  5 +++++
>   builtin/repo.c              |  7 +++++++
>   t/t1900-repo-info.sh        | 10 ++++++++++
>   3 files changed, 22 insertions(+)
> > diff --git a/Documentation/git-repo.adoc b/Documentation/git-repo.adoc
> index 42262c1983..d17d911ec6 100644
> --- a/Documentation/git-repo.adoc
> +++ b/Documentation/git-repo.adoc
> @@ -95,6 +95,11 @@ In order to obtain a set of values from `git repo info`, you should provide
>   the keys that identify them. Here's a list of the available keys and the
>   values that they return:
>   > +`paths.git_dir`::
> +	The path to the Git directory for the repository (equivalent to
> +	`git rev-parse --git-dir`).
> +
> +
>   `layout.bare`::
>   	`true` if this is a bare repository, otherwise `false`.
>   > diff --git a/builtin/repo.c b/builtin/repo.c
> index 55f9b9095c..3067107cad 100644
> --- a/builtin/repo.c
> +++ b/builtin/repo.c
> @@ -66,11 +66,18 @@ static int get_references_format(struct repository *repo, struct strbuf *buf)
>   	return 0;
>   }
>  ...

> +static int get_paths_git_dir(struct repository *repo, struct strbuf *buf)
> +{
> +	strbuf_addstr(buf, repo_get_git_dir(repo));
> +	return 0;
> +}
> +

...But your implementation here doesn't quite feel right. Check the git-rev-parse documentation: the output of the --git-dir argument is context-aware and depends on your current directory.

If you are in the root directory of the repository, it gives '.git'; And if you are in some subdirectory of the repository , it gives '/home/user/.../repo-root/.../.git'. I don't think simply calling 'repo_get_git_dir(repo)' will achieve this functionality.

>   /* repo_info_field keys must be in lexicographical order */
>   static const struct repo_info_field repo_info_field[] = {
>   	{ "layout.bare", get_layout_bare },
>   	{ "layout.shallow", get_layout_shallow },
>   	{ "object.format", get_object_format },
> +	{ "paths.git_dir", get_paths_git_dir },
>   	{ "references.format", get_references_format },
>   };
>   > diff --git a/t/t1900-repo-info.sh b/t/t1900-repo-info.sh
> index a9eb07abe8..63be0849c4 100755
> --- a/t/t1900-repo-info.sh
> +++ b/t/t1900-repo-info.sh
> @@ -149,4 +149,14 @@ test_expect_success 'git repo info --keys uses lines as its default output forma
>   	test_cmp expect actual
>   '
>   ...

> +test_expect_success 'paths.git_dir matches rev-parse --git-dir' '
> +	git init repo &&
> +	(
> +		cd repo &&
> +		git repo info paths.git_dir >actual &&
> +		echo "paths.git_dir=$(git rev-parse --git-dir)" >expect &&
> +		test_cmp expect actual
> +	)
> +'
> +
>   test_done

And you’ve only provided tests for the root directory here, which I don’t think is sufficient. That said, considering that you’ve likely misunderstood how to use the --git-dir parameter, this is understandable.

Next time you create a similar patch, I think you should take a close look at the documentation and source code first, and try using the existing commands a few times on your own to understand how they work, right? ;)

Regards,

Yuchen

gitgitgadget-git · 2026-04-07T06:46:03Z

User Tian Yuchen <a3205153416@gmail.com> has been added to the cc: list.

gitgitgadget-git · 2026-04-07T08:03:08Z

Karthik Nayak wrote on the Git mailing list (how to reply to this email):

"Jayesh Daga via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: jayesh0104 <jayeshdaga99@gmail.com>
>
> Introduce a new repo info key `paths.git_dir` to expose the
> repository's gitdir path, equivalent to `git rev-parse --git-dir`.
>
> This improves consistency and allows tools to retrieve the gitdir
> path without invoking external commands.
>
> The implementation adds support in repo.c and integrates it into
> the repo info reporting mechanism. Documentation is updated to
> describe the new key, and tests are added to verify that the value
> matches the output of `git rev-parse --git-dir`.
>

Hello Jayesh,

Seeing from the people CC'd I'm assuming that you're interested in
applying for the GSoC.

As such, we encourage GSoC contributors to work on micro-projects as
listed on our GSoC website and also to read the guidelines we've laid
out [1] [2].

I would also mention that we do not recommend getting started on a
project, unless you're selected.

Now specifically for this project, there is still no decision made about
using relative paths vs absolute paths, I've highlighted this in one of
the candidates proposals [3]. I would suggest getting involved in that
discussion and coming to a conclusion before starting work on it.

[1]: https://git.github.io/General-Microproject-Information/
[2]: https://git.github.io/General-Application-Information/
[3]: https://lore.kernel.org/git/CAOLa=ZTtNSZ904v0-SN16jAis7gK4=MVj1g_5CGdbmaBopeZkg@mail.gmail.com/#t

Regards,
Karthik

[snip]

gitgitgadget-git · 2026-04-07T08:07:06Z

Tian Yuchen wrote on the Git mailing list (how to reply to this email):

Hi Jayesh,

On 3/18/26 00:55, Jayesh Daga via GitGitGadget wrote:
> From: jayesh0104 <jayeshdaga99@gmail.com>
> > Introduce a new repo info key `paths.git_dir` to expose the
> repository's gitdir path, equivalent to `git rev-parse --git-dir`.

Here you promise in the commit message that paths.git_dir and git rev-parse --git-dir are equivalent...

> > This improves consistency and allows tools to retrieve the gitdir
> path without invoking external commands.
> > The implementation adds support in repo.c and integrates it into
> the repo info reporting mechanism. Documentation is updated to
> describe the new key, and tests are added to verify that the value
> matches the output of `git rev-parse --git-dir`.
> > Signed-off-by: jayesh0104 <jayeshdaga99@gmail.com>
> ---
>      repo: add paths.git_dir to 'git repo info'
>      >      Teach git repo info a new key, paths.git_dir, which reports the
>      repository’s gitdir path (equivalent to git rev-parse --git-dir).
>      >      Documentation and tests are included.
>      >      Tests:
>      >       * make test T=t1900-repo-info.sh
> > Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2242%2Fjayesh0104%2Fmaster-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2242/jayesh0104/master-v1
> Pull-Request: https://github.com/git/git/pull/2242
> >   Documentation/git-repo.adoc |  5 +++++
>   builtin/repo.c              |  7 +++++++
>   t/t1900-repo-info.sh        | 10 ++++++++++
>   3 files changed, 22 insertions(+)
> > diff --git a/Documentation/git-repo.adoc b/Documentation/git-repo.adoc
> index 42262c1983..d17d911ec6 100644
> --- a/Documentation/git-repo.adoc
> +++ b/Documentation/git-repo.adoc
> @@ -95,6 +95,11 @@ In order to obtain a set of values from `git repo info`, you should provide
>   the keys that identify them. Here's a list of the available keys and the
>   values that they return:
>   > +`paths.git_dir`::
> +	The path to the Git directory for the repository (equivalent to
> +	`git rev-parse --git-dir`).
> +
> +
>   `layout.bare`::
>   	`true` if this is a bare repository, otherwise `false`.
>   > diff --git a/builtin/repo.c b/builtin/repo.c
> index 55f9b9095c..3067107cad 100644
> --- a/builtin/repo.c
> +++ b/builtin/repo.c
> @@ -66,11 +66,18 @@ static int get_references_format(struct repository *repo, struct strbuf *buf)
>   	return 0;
>   }
>  ...

> +static int get_paths_git_dir(struct repository *repo, struct strbuf *buf)
> +{
> +	strbuf_addstr(buf, repo_get_git_dir(repo));
> +	return 0;
> +}
> +

...But your implementation here doesn't quite feel right. Check the git-rev-parse documentation: the output of the --git-dir argument is context-aware and depends on your current directory.

If you are in the root directory of the repository, it gives '.git'; And if you are in some subdirectory of the repository , it gives '/home/user/.../repo-root/.../.git'. I don't think simply calling 'repo_get_git_dir(repo)' will achieve this functionality.

>   /* repo_info_field keys must be in lexicographical order */
>   static const struct repo_info_field repo_info_field[] = {
>   	{ "layout.bare", get_layout_bare },
>   	{ "layout.shallow", get_layout_shallow },
>   	{ "object.format", get_object_format },
> +	{ "paths.git_dir", get_paths_git_dir },
>   	{ "references.format", get_references_format },
>   };
>   > diff --git a/t/t1900-repo-info.sh b/t/t1900-repo-info.sh
> index a9eb07abe8..63be0849c4 100755
> --- a/t/t1900-repo-info.sh
> +++ b/t/t1900-repo-info.sh
> @@ -149,4 +149,14 @@ test_expect_success 'git repo info --keys uses lines as its default output forma
>   	test_cmp expect actual
>   '
>   ...

> +test_expect_success 'paths.git_dir matches rev-parse --git-dir' '
> +	git init repo &&
> +	(
> +		cd repo &&
> +		git repo info paths.git_dir >actual &&
> +		echo "paths.git_dir=$(git rev-parse --git-dir)" >expect &&
> +		test_cmp expect actual
> +	)
> +'
> +
>   test_done

And you’ve only provided tests for the root directory here, which I don’t think is sufficient. That said, considering that you’ve likely misunderstood how to use the --git-dir parameter, this is understandable.

Next time you create a similar patch, I think you should take a close look at the documentation and source code first, and try using the existing commands a few times on your own to understand how they work, right? ;)

Regards,

Yuchen

github-project-automation bot added this to Op-Amp Frequency Response and Applications Suite Mar 17, 2026

github-project-automation bot moved this to Todo in Op-Amp Frequency Response and Applications Suite Mar 17, 2026

gitgitgadget-git bot added the new user label Mar 17, 2026

jayesh0104 marked this pull request as draft March 17, 2026 14:30

jayesh0104 marked this pull request as ready for review March 17, 2026 15:38

jayesh0104 force-pushed the master branch from f07605e to c71df10 Compare March 17, 2026 15:41

leuasseurfarrelds247-arch reviewed Mar 17, 2026

View reviewed changes

jayesh0104 force-pushed the master branch from c71df10 to 76199b0 Compare March 17, 2026 15:48

jayesh0104 force-pushed the master branch from 76199b0 to 5a8165b Compare March 17, 2026 16:42

Conversation

jayesh0104 commented Mar 17, 2026 • edited by gitgitgadget-git bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Welcome to GitGitGadget

Contributing the patches

Need help?

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

leuasseurfarrelds247-arch left a comment

Choose a reason for hiding this comment

Uh oh!

jayesh0104 commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

dscho commented Mar 17, 2026

Uh oh!

jayesh0104 commented Mar 17, 2026

Uh oh!

dscho commented Mar 17, 2026

Uh oh!

dscho commented Mar 17, 2026

Uh oh!

jayesh0104 commented Mar 17, 2026

Uh oh!

dscho commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

jayesh0104 commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Mar 17, 2026

Uh oh!

dscho commented Mar 17, 2026

Uh oh!

gitgitgadget-git bot commented Apr 7, 2026

Uh oh!

gitgitgadget-git bot commented Apr 7, 2026

Uh oh!

gitgitgadget-git bot commented Apr 7, 2026

Uh oh!

gitgitgadget-git bot commented Apr 7, 2026

Uh oh!

gitgitgadget-git bot commented Apr 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

jayesh0104 commented Mar 17, 2026 •

edited by gitgitgadget-git bot

Loading