From: <rsbecker@nexbridge•com>
To: "'Kristoffer Haugsbakk'" <kristofferhaugsbakk@fastmail•com>,
"'usharerose'" <ushareroses@gmail•com>, <git@vger•kernel.org>
Subject: RE: [DISCUSS] validation on git config user.email
Date: Sun, 14 Sep 2025 12:59:56 -0400 [thread overview]
Message-ID: <007701dc2599$02b6ca30$08245e90$@nexbridge.com> (raw)
In-Reply-To: <88e9b975-70a5-4773-bd08-634e56c491c6@app.fastmail.com>
On September 14, 2025 7:18 AM, Kristoffer Haugsbakk wrote:
>On Fri, Sep 12, 2025, at 17:00, rsbecker@nexbridge•com wrote:
>> On September 12, 2025 12:13 AM, usharerose wrote:
>>>I'm a Git user and curious about a specific aspect of Git's design
>>>regarding the 'user.email' configuration.
>>>
>>>Git allows any kind of values without restriction when setting
>>>'user.email' via 'git config' (e.g., `git config user.email
"not-a-valid-email-
>address"`).
>>>
>>>I'm interested in understanding the design philosophy or historical
>>>reasons behind this 'lack' of validation.
>>>
>>>I've glanced through the documentations, archived emails, or forum
>>>topics, but couldn't find a definitive or official statement.
>>>
>>>Thanks for your time and insights.
>>
>> Some customers integrate single sign-on (SSO) via the user.email value.
>> In the case
>> of one customer I helped, the value is an SSO token used by GitHub for
>> their integration. The token value does not conform to any valid email
>> address format.
>> Adding an email validation will lock them out of using git.
>
>That sounds unreasonable.
In what way, may I ask? I have personally seen this done. Their core.email
value is not a valid user name. It is a token with no @ or . characters. It
is an alphanumeric string.
next prev parent reply other threads:[~2025-09-14 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 4:13 [DISCUSS] validation on git config user.email usharerose
2025-09-12 15:00 ` rsbecker
2025-09-12 16:29 ` Junio C Hamano
2025-09-12 18:06 ` usharerose
2025-09-12 16:52 ` usharerose
2025-09-12 17:23 ` rsbecker
2025-09-12 17:44 ` usharerose
2025-09-14 11:17 ` Kristoffer Haugsbakk
2025-09-14 16:59 ` rsbecker [this message]
2025-09-12 15:13 ` Konstantin Ryabitsev
2025-09-12 15:39 ` Thomas Guyot
2025-09-12 18:02 ` usharerose
2025-09-14 11:58 ` Kristoffer Haugsbakk
2025-09-15 13:40 ` usharerose
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='007701dc2599$02b6ca30$08245e90$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=ushareroses@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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