From: <rsbecker@nexbridge.com>
To: "'usharerose'" <ushareroses@gmail.com>, <git@vger.kernel.org>
Subject: RE: [DISCUSS] validation on git config user.email
Date: Fri, 12 Sep 2025 11:00:25 -0400 [thread overview]
Message-ID: <071101dc23f5$fbf06e30$f3d14a90$@nexbridge.com> (raw)
In-Reply-To: <CAJKmQvf-sLxowLJLitvqDmyL1BXXDK+anDE2jaBSEabApMNVoQ@mail.gmail.com>
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.
--Randall
next prev parent reply other threads:[~2025-09-12 15:00 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 [this message]
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
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='071101dc23f5$fbf06e30$f3d14a90$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=ushareroses@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.