Hello, Is there a way to gpg sign pull request via web interface.
Currently it is showing this, so I suppose it is impossible?
image
test repository.
GPG sign Pull Request via web ui? #432
Closed
opened 2021年04月29日 15:25:49 +02:00 by zabihexes
·
2 comments
zabihexes
commented 2021年04月29日 15:25:49 +02:00
Hello, Is there a way to gpg sign pull request via web interface.
Currently it is showing this, so I suppose it is impossible?

[test repository](https://codeberg.org/Yui/test/pulls/2).
6.8 KiB
fnetX
commented 2021年04月29日 15:57:13 +02:00
Hey, please also see #400. As far as I understand the matter, we'd have to put a server-wide Gitea GPG key that signs every commit done by the web UI.
This is apparently an undecided matter, but we'll take this into consideration.
Per-user keys would also be a nice thing imho, so a user could upload a second web-key. That sounds safer than having a server-wide key that affects all the projects to me.
Hey, please also see #400. As far as I understand the matter, we'd have to put a server-wide Gitea GPG key that signs every commit done by the web UI.
This is apparently an undecided matter, but we'll take this into consideration.
Per-user keys would also be a nice thing imho, so a user could upload a second web-key. That sounds safer than having a server-wide key that affects all the projects to me.
fnetX
added the 2021年04月29日 15:57:27 +02:00
duplicate
question
labels
zabihexes
commented 2021年04月29日 23:36:39 +02:00
Ok, Thanks. I am closing this since its duplicate.
Ok, Thanks. I am closing this since its duplicate.
zabihexes
closed this issue 2021年04月29日 23:36:39 +02:00
Sign in to join this conversation.
Labels
Clear labels
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No labels
accessibility
bug
bug
infrastructure
Codeberg
contributions welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
please chill
we are volunteers
public relations
question
question
user support
s/Forgejo
s/Forgejo/migration
s/Pages
s/Weblate
s/Woodpecker
security
service
upstream
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
Codeberg/Community#432
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
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?