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

Changing email account doesn't release that email #17519

Closed
isyq opened this issue Nov 2, 2021 · 4 comments · Fixed by #17549
Closed

Changing email account doesn't release that email #17519

isyq opened this issue Nov 2, 2021 · 4 comments · Fixed by #17549
Labels
Milestone

Comments

@isyq
Copy link

isyq commented Nov 2, 2021

I set the admin account to xxx@mail.com, after built everything up, I change it to yyy@mail.com.
Now I try to set a new user with that email(xxx@mail.com), it always alerts the email is already existed.

@lunny
Copy link
Member

lunny commented Nov 2, 2021

What's the version of you Gitea instance?

@lunny lunny added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Nov 2, 2021
@isyq
Copy link
Author

isyq commented Nov 3, 2021

"gitea.exe --version" shows: Gitea version 1.15.6 built with GNU Make 4.1, go1.16.9 : bindata, sqlite, sqlite_unlock_notify.

@lunny
Copy link
Member

lunny commented Nov 3, 2021

How did you change the old user's email to yyy@mail.com?

@isyq
Copy link
Author

isyq commented Nov 3, 2021

Login admin's home page -> 'Site administration' page -> User accounts -> Change itself email address.

@lunny lunny added type/bug and removed issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail labels Nov 4, 2021
@lunny lunny added this to the 1.15.7 milestone Nov 4, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants