github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 06:24:14 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Support adding GPG signing sub-key #6542

New Issue
Closed
opened 2025-11-02 06:58:54 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 06:58:54 -06:00
Owner
Copy Link

Originally created by @etanot on GitHub (Dec 17, 2020).

Type : Feature request

Description

As @a1012112796 has mentioned in https://github.com/go-gitea/gitea/issues/14009#issuecomment-746558233 "Now gitea only allow add public gpg keys bounded with the user's email", it would be nice if Gitea also support adding GPG sub-key, just like mention in issue https://github.com/go-gitea/gitea/issues/14009.

Originally created by @etanot on GitHub (Dec 17, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> **Type** : Feature request ## Description As @a1012112796 has mentioned in https://github.com/go-gitea/gitea/issues/14009#issuecomment-746558233 "Now gitea only allow add public gpg keys bounded with the user's email", it would be nice if Gitea also support adding GPG sub-key, just like mention in issue https://github.com/go-gitea/gitea/issues/14009.
GiteaMirror added the type/proposal label 2025-11-02 06:58:54 -06:00
GiteaMirror commented 2025-11-02 06:58:54 -06:00
Author
Owner
Copy Link

@quhsi commented on GitHub (Jan 2, 2021):

Currently, the email address cannot be kept private when using the PGP key feature. So this issue is more a bugfix than a feature.

@quhsi commented on GitHub (Jan 2, 2021): Currently, the email address cannot be kept private when using the PGP key feature. So this issue is more a bugfix than a feature.
GiteaMirror commented 2025-11-02 06:58:55 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 2, 2021):

#14054 was an attempt at fixing this issue - however, due to the lack of real life testing of this feature I've had to move it to the 1.15 milestone. Hopefully we'll merge after the merge window for 1.14 is closed.

If you really want this feature in 1.14 you will need to download and test this PR to ensure that it does what you want.

@zeripath commented on GitHub (Mar 2, 2021): #14054 was an attempt at fixing this issue - however, due to the lack of real life testing of this feature I've had to move it to the 1.15 milestone. Hopefully we'll merge after the merge window for 1.14 is closed. If you really want this feature in 1.14 you will need to download and test this PR to ensure that it does what you want.
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/proposal
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#6542
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?