github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-17 06:32:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Add support for multiple emails per user #2345

New Issue
Closed
opened 2025-11-02 04:33:27 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:33:27 -06:00
Owner
Copy Link

Originally created by @RyanSquared on GitHub (Sep 19, 2018).

  • Gitea version (or commit ref):

  • Git version: N/A

  • Operating system: Linux [hostname] 4.9.0-8-amd64 #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 creation

  • Database (use [x]):

    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

  • Can you reproduce the bug at https://try.gitea.io:

    • Yes (provide example URL)
    • No
    • Not relevant

  • 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.

Originally created by @RyanSquared on GitHub (Sep 19, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: N/A - Operating system: Linux [hostname] 4.9.0-8-amd64 #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 creation - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - 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.
GiteaMirror added the type/question label 2025-11-02 04:33:27 -06:00
GiteaMirror commented 2025-11-02 04:33:28 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 19, 2018):

Gitea already does support multiple emails, see user settings

@lafriks commented on GitHub (Sep 19, 2018): Gitea already does support multiple emails, see user settings
GiteaMirror commented 2025-11-02 04:33:28 -06:00
Author
Owner
Copy Link

@RyanSquared commented on GitHub (Sep 19, 2018):

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?

@RyanSquared commented on GitHub (Sep 19, 2018): 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?
GiteaMirror commented 2025-11-02 04:33:29 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 19, 2018):

It just historicaly how it was easier to add. GitHub also has it this way

@lafriks commented on GitHub (Sep 19, 2018): It just historicaly how it was easier to add. GitHub also has it this way
GiteaMirror commented 2025-11-02 04:33:29 -06:00
Author
Owner
Copy Link

@RyanSquared commented on GitHub (Sep 19, 2018):

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 gpg --export --armor ryan@hashbang.sh, but after putting it into Gitea, it was listed as vandor2012@gmail.com.

@RyanSquared commented on GitHub (Sep 19, 2018): 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 `gpg --export --armor ryan@hashbang.sh`, but after putting it into Gitea, it was listed as `vandor2012@gmail.com`.
GiteaMirror commented 2025-11-02 04:33:29 -06:00
Author
Owner
Copy Link

@RyanSquared commented on GitHub (Sep 19, 2018):

To clarify on the issue: Gitea expects the key to be made from vandor2012@gmail.com. However, the signature is parsed as coming from ryan@hashbang.sh

@RyanSquared commented on GitHub (Sep 19, 2018): To clarify on the issue: Gitea expects the key to be made from `vandor2012@gmail.com`. However, the signature is parsed as coming from `ryan@hashbang.sh`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2345
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?