Gitea: [Question] Why when I merge from web commits are not verified?
In GitHub if you merge a PR that commit will be marked as verified. In Gitea merge commits are not verified. Am I missing something?
pando85
All 6 comments
GitHub generates inrernal pgp key for each user and uses that for commits from web UI and merges
lafriks
on 5 Feb 2019
I think this is not priority but are you thinking in implement this feature?
pando85
on 6 Feb 2019
currently there is no plans for this
lafriks
on 6 Feb 2019
I was looking in to this today and found something interesting. GitHub actually does not generate a key for each user, it only uses one. I had also been under the assumption that each user had their own internal key.
In their article about GPG they reveal the link to their GPG key they use for "web flow".
I only mention this in case someone does pick this up, perhaps it would make sense to just generate one internal key for the specific Gitea instance rather than one internal key for each user?
jolheiser
on 28 Feb 2019
Nice.. Thanks @jolheiser
adelowo
on 28 Feb 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
![stale[bot] picture](https://avatars3.githubusercontent.com/in/1724?v=4&s=40)
stale[bot]
on 30 Apr 2019
Related issues
cookiengineer
路
3Comments
ghost
路
3Comments
lunny
路
3Comments
kolargol
路
3Comments
thehowl
路
3Comments
Most helpful comment
I was looking in to this today and found something interesting. GitHub actually does not generate a key for each user, it only uses one. I had also been under the assumption that each user had their own internal key.
In their article about GPG they reveal the link to their GPG key they use for "web flow".
I only mention this in case someone does pick this up, perhaps it would make sense to just generate one internal key for the specific Gitea instance rather than one internal key for each user?