Git development
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Giorgos Gasparis" <gasp.giorgos@gmail.com>, git@vger.kernel.org
Subject: Re: [Feature Proposal] Add a built-in 'git whoami' command
Date: Tue, 31 Mar 2026 18:43:02 +0200	[thread overview]
Message-ID: <fab20df3-248b-4590-9b3e-e7601404df55@app.fastmail.com> (raw)
In-Reply-To: <CALCP2CjymE-i9TsKB8TmW_0M=ZDbtLPzZFpx4-ba01164b1MOA@mail.gmail.com>

On Tue, Mar 31, 2026, at 16:57, Giorgos Gasparis wrote:
> I would like to propose adding a native git whoami command to Git to
> easily check the currently active identity.
>
> Currently, users have to run two separate commands (git config
> user.name and git config user.email) to check this. This is a frequent
> friction point for developers balancing work and personal repositories
> who want to double-check their active profile before committing.
>
> To solve this locally, I currently use the following alias in my .gitconfig:
>
> [alias] whoami = !echo "👤 $(git config user.name) | 📧 $(git config
> user.email)"

Strange. I was looking at an example from git-interpret-trailers(1) today.

    $ git config trailer.sign.cmd 'echo "$(git config user.name) <$(git config user.email)>"'

And “git-whoami(1)?” jumped in to my mind.

You can kind of get that with [which Junio mentioned after I wrote this draft]

    git var GIT_AUTHOR_IDENT | sed -e 's/> .*/>/'

Too bad with the postprocessing needed for the timestamp.

> Having a built-in command that provides this kind of unified,
> single-line output natively (even as standard plain text without
> emojis) would be a great quality-of-life improvement for the wider
> community so they don't have to build custom aliases.

A problem (subjectively) is that there are already 147 git(1) commands.

      parent reply	other threads:[~2026-03-31 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 14:57 [Feature Proposal] Add a built-in 'git whoami' command Giorgos Gasparis
2026-03-31 16:26 ` Junio C Hamano
2026-03-31 16:43 ` Kristoffer Haugsbakk [this message]

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=fab20df3-248b-4590-9b3e-e7601404df55@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=gasp.giorgos@gmail.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox