github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-10 15:39:40 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

More descriptive message when signing key recognised by unverified #9319

New Issue
Open
opened 2025-11-02 08:35:11 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 08:35:11 -06:00
Owner
Copy Link

Originally created by @tecosaur on GitHub (Aug 2, 2022).

Feature Description

At the moment, Gitea does not distinguish between a signed commit's key being:

  • unknown, and
  • recognised from /user/settings/keys, but unverified

In both cases, "No known key found for this signature in database" is shown.

This can be a little confusing when the key is known, just not verified. See #20597.

This is a minor thing, but it would be a UX improvement if the message was "the signing key used is not verified" (or similar) rather than not known at all.

Screenshots

image

Originally created by @tecosaur on GitHub (Aug 2, 2022). ### Feature Description At the moment, Gitea does not distinguish between a signed commit's key being: - unknown, and - recognised from `/user/settings/keys`, but unverified In both cases, "No known key found for this signature in database" is shown. This can be a little confusing when the key *is* known, just not verified. See #20597. This is a minor thing, but it would be a UX improvement if the message was "the signing key used is not verified" (or similar) rather than not known at all. ### Screenshots ![image](https://user-images.githubusercontent.com/20903656/182272649-47ab949d-1c3b-405c-b8f9-1eae4aea9791.png)
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:35:11 -06:00
GiteaMirror commented 2025-11-02 08:35:12 -06:00
Author
Owner
Copy Link

@twisted-nematic57 commented on GitHub (Nov 15, 2022):

I also can't verify my key for some unknown reason!! Checked the logs, fails with error <nil>

@twisted-nematic57 commented on GitHub (Nov 15, 2022): I also can't verify my key for some unknown reason!! Checked the logs, fails with error `<nil>`
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/feature 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#9319
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?