Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow blank email #21704

Open
badiku opened this issue Nov 7, 2022 · 8 comments
Open

allow blank email #21704

badiku opened this issue Nov 7, 2022 · 8 comments
Labels
proposal/rejected We have reviewed the proposal but disagree in that it should not be implemented into Gitea. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@badiku
Copy link

badiku commented Nov 7, 2022

Feature Description

hi, for decades we never use email. why every account should have an email ?

I wish email is not a required field when create a new user.

I modified custom\templates\admin\user\new.tmpl but it seems that the requirement is deep in server backend.

please add an option to disable email requirement, or can someone kindly point to me where to modify it by myself.

Screenshots

No response

@badiku badiku added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Nov 7, 2022
@lunny
Copy link
Member

lunny commented Nov 7, 2022

Since git requires an email, I don't think an email address could be ignored?

@lunny lunny removed the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Nov 7, 2022
@badiku
Copy link
Author

badiku commented Nov 7, 2022

I trid to remove some valid function, so it can transfer register data with blank email from web to backend, but still failed:

[ERROR] [6368b1b7] CreateUser: e-mail already in use [email: ]

so it is deeply required by some code.

Since git requires an email,

but git allow blank email. for years I always begin my new git environment by this : git config --global user.email ""

and there is no problem at all.

if you use git as a standard, I think we should allow blank email, just like git does.

the fact is , nowadays email is never used, except for register github.

specially , for internal team usage , there is no need to fore use email.

@lunny
Copy link
Member

lunny commented Nov 7, 2022

You can use false email address like myname@myorg.com and disable email confirmation in app.ini

@badiku
Copy link
Author

badiku commented Nov 7, 2022

yeah, I already did this. just tired to type a fake email for each person.

I'd like to change it by myself. but seems a little complicated...

@eric-j-ason
Copy link

Since git requires an email, I don't think an email address could be ignored?

In addition to Git not really forcing you to use an email address, a user might not even want to create commits, only read the source code and use the issue tracker.

By the way, Gitea doesn't even allow addresses with only a top domain after the @, such as invalid@invalid and user@com, although it is my understanding that those are valid.

@lunny lunny added the proposal/rejected We have reviewed the proposal but disagree in that it should not be implemented into Gitea. label Oct 28, 2024
@lunny
Copy link
Member

lunny commented Oct 28, 2024

This is too complicated and I couldn't find more benefit to implementing it.

@Mosch0512
Copy link

how to disable email conformation in app ini.
Personaly i would need that feature too.
But only from the admins perspective

@MaxEden
Copy link

MaxEden commented Jan 6, 2025

Using gitea for internal repo manager is kinda hard right now. There are no private invites so I have to create user accounts manually, so I have to make up email addresses. It's not elegant to put it mildly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal/rejected We have reviewed the proposal but disagree in that it should not be implemented into Gitea. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants