RE: [DISCUSS] validation on git config user.email

From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date: Sep 12, 2025, 15:00 UTC
Message-ID: <071101dc23f5$fbf06e30$f3d14a90$@nexbridge.com>
In-Reply-To: <CAJKmQvf-sLxowLJLitvqDmyL1BXXDK+anDE2jaBSEabApMNVoQ@mail.gmail.com>

On September 12, 2025 12:13 AM, usharerose wrote:

Show 13 quoted lines

>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