Sign Pull Requests with induvidual keys #9963

Open
opened 2025-11-02 08:54:24 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @iiinnniii on GitHub (Dec 11, 2022).

Feature Description

At the moment it is possible to automatically sign a resulting merge commit of a pull request via configuring Gitea like mentioned here. The problem with that is, that this will always lead to the same signature provided by the server and it is not possible at the moment for Collaborators to sign the resulting merge commit themselves (at least I found no options to do that).

To me it seems that this current way to sign the resulting merge commits of a pull request is more a workaround to make it possible to have the "Require Signed Commits" setting enabled, but it does not really add much value.

At the end of the day a resulting merge commit of a pull request should ideally be also signable by an individual like other commits.

I do not have that much insight on how the signing process works in git, but wouldn't is be possible to output the commit in the UI and demand it to be signed via Kleopatra or some other gpg frontend and then the user provides the signed commit as a response in the UI?

Screenshots

No response

Originally created by @iiinnniii on GitHub (Dec 11, 2022). ### Feature Description At the moment it is possible to automatically sign a resulting merge commit of a pull request via configuring Gitea like mentioned [here](https://docs.gitea.io/en-us/signing/). The problem with that is, that this will always lead to the same signature provided by the server and it is not possible at the moment for Collaborators to sign the resulting merge commit themselves (at least I found no options to do that). To me it seems that this current way to sign the resulting merge commits of a pull request is more a workaround to make it possible to have the "Require Signed Commits" setting enabled, but it does not really add much value. At the end of the day a resulting merge commit of a pull request should ideally be also signable by an individual like other commits. I do not have that much insight on how the signing process works in git, but wouldn't is be possible to output the commit in the UI and demand it to be signed via Kleopatra or some other gpg frontend and then the user provides the signed commit as a response in the UI? ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 08:54:24 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9963