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

Trust the github public key per default #6328

New Issue
Closed
opened 2025-11-02 06:52:43 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 06:52:43 -06:00
Owner
Copy Link

Originally created by @enaut on GitHub (Nov 17, 2020).

Description

When pushing a Github repository the commits signed with Github are "untrusted". Wouldn't it make sense to be able to add this key to be trusted either as a setting or as default?

The public Github key that signs all webcommits is: 4AEE18F83AFDEB23 available here: https://github.com/web-flow.gpg

I think it could make sense to add some Keys as trusted by default (of course this should be configurable).

For maximum beauty it would of course be cool to automagically link the appropriate Github profile.

Originally created by @enaut on GitHub (Nov 17, 2020). ## Description When pushing a Github repository the commits signed with Github are "untrusted". Wouldn't it make sense to be able to add this key to be trusted either as a setting or as default? The public Github key that signs all webcommits is: 4AEE18F83AFDEB23 available here: https://github.com/web-flow.gpg I think it could make sense to add some Keys as trusted by default (of course this should be configurable). For maximum beauty it would of course be cool to automagically link the appropriate Github profile.
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
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#6328
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?