Hi all,

I’ve been looking at the "git repo" command recently, mostly comparing
"git repo info" with what I usually reach for via "git rev-parse".

One thing I noticed is that git repo info currently reports repository
properties like layout and formats, but none of the repository paths
that scripts often need.

For example, as of now:

git rev-parse --git-dir
git rev-parse --common-dir
git rev-parse --git-path hooks

are commonly used by scripts and tooling to figure out where things
actually live on disk.

I wanted to ask whether it would make sense for git repo info to
eventually expose some of these as structured keys, starting with
something minimal like "git-dir".

My idea is not to completely replace rev-parse, but to let "git repo
info" act as a more discoverable, descriptive interface for repository
metadata, including paths, where appropriate.

One question I am unsure about is whether such paths should be
reported as absolute or relative (for example, relative to the working
tree or invocation directory), and whether git-dir would be a
reasonable first step before considering others.

I wanted to ask first before making any changes, and would appreciate
guidance on whether this direction makes sense.

Thanks,
Pushkar