-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Add support for multiple emails per user #4957
Comments
Gitea already does support multiple emails, see user settings |
Sorry about that. I saw on the landing page for the settings that there was one "Email Address". Why are there two UIs for the same thing? |
It just historicaly how it was easier to add. GitHub also has it this way |
GitHub has a dedicated section for managing emails. Not sure whether that's new or not with the redesign. GitHub also mentions that it's the "primary" email, which indicates you can have at least a secondary. Onto another issue, it appears as though only one email is being parsed from my key. GitHub says the key is: "Email addresses: ryan@hashbang.sh vandor2012@gmail.com" I know that I ran |
To clarify on the issue: Gitea expects the key to be made from |
Gitea version (or commit ref):
Git version: N/A
Operating system: Linux [hostname] 4.9.0-8-amd64 Rename import paths: "github.com/gogits/gogs" -> "github.com/go-gitea/gitea" #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux running under Docker:
gitea/gitea:latest
updated as of this issue creationDatabase (use
[x]
):Can you reproduce the bug at https://try.gitea.io:
Log gist:
Description
GitHub allows for users to add multiple emails, listing one as the "primary" email. This is useful as it allows users to have various GPG keys with different emails associated with an account without having verification issues.
This feature is essential for Gitea's verification, as right now my commits are showing as unverified, because the email used to sign them is different than the one associated with my account.
The text was updated successfully, but these errors were encountered: