[PR #476] [CLOSED] [WIP] GPG Verification (#425) #15406

New Issue

GiteaMirror · 2025-11-02T11:45:50-06:00

GiteaMirror commented

2025-11-02 11:45:50 -06:00

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/476
Author: @bkcsoft
Created: 12/25/2016
Status: ❌ Closed

Base: master ← Head: bkcsoft/425-gpg-verification

📝 Commits (6)

f64213d Create gpg api methods
af4fe8a Register route
a14a338 Implementing api routing and all necessarry code in progress
adb8321 Catch up with changes
1dd4561 Test UI
2e78044 ...

📊 Changes

10 files changed (+272 additions, -2 deletions)

View changed files

📝 models/error.go (+20 -0)
➕ models/gpg_key.go (+105 -0)
📝 routers/api/v1/api.go (+7 -0)
📝 routers/api/v1/convert/convert.go (+20 -0)
📝 routers/api/v1/repo/key.go (+10 -0)
➕ routers/api/v1/user/gpg_keys.go (+93 -0)
📝 routers/repo/commit.go (+1 -0)
📝 routers/repo/view.go (+1 -0)
📝 templates/repo/commits_table.tmpl (+8 -1)
📝 templates/repo/view_list.tmpl (+7 -1)

📄 Description

Migrated from https://github.com/gogits/gogs/pull/3127

https://github.com/gogits/gogs/pull/3127#issuecomment-228626156

I didn't tackle the part of the verification and I didn't have time to go further but i will re-put myself on it on the next days. Doing it in the front-end could be done easely. It just need the API to get the user public key from gogs like https://developer.github.com/v3/users/keys/. On the other hand, i don't thinks it would be too much work for the backen to do it. I have to think about it but at first at will implement the API because in both case they will be needed (or at least usefull)

Closes #425

@sapk would you like to continue this by yourself? or mind filling me in on whats left to be done 🙂

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/476 **Author:** [@bkcsoft](https://github.com/bkcsoft) **Created:** 12/25/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `bkcsoft/425-gpg-verification` --- ### 📝 Commits (6) - [`f64213d`](https://github.com/go-gitea/gitea/commit/f64213d82f28b44ad93fb2eba8881002d726d487) Create gpg api methods - [`af4fe8a`](https://github.com/go-gitea/gitea/commit/af4fe8a5a84fa217714a8d365983a1862b954b14) Register route - [`a14a338`](https://github.com/go-gitea/gitea/commit/a14a338419ea52275b1818dd0ba3ef687a705e23) Implementing api routing and all necessarry code in progress - [`adb8321`](https://github.com/go-gitea/gitea/commit/adb8321ddb7582b21e69321ad896bb626dc68ed6) Catch up with changes - [`1dd4561`](https://github.com/go-gitea/gitea/commit/1dd4561aa5a48502986e9b52da6f6ea4cdc8bb2c) Test UI - [`2e78044`](https://github.com/go-gitea/gitea/commit/2e78044036241ae14a9d235ebda5c8822a844488) ... ### 📊 Changes **10 files changed** (+272 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `models/error.go` (+20 -0) ➕ `models/gpg_key.go` (+105 -0) 📝 `routers/api/v1/api.go` (+7 -0) 📝 `routers/api/v1/convert/convert.go` (+20 -0) 📝 `routers/api/v1/repo/key.go` (+10 -0) ➕ `routers/api/v1/user/gpg_keys.go` (+93 -0) 📝 `routers/repo/commit.go` (+1 -0) 📝 `routers/repo/view.go` (+1 -0) 📝 `templates/repo/commits_table.tmpl` (+8 -1) 📝 `templates/repo/view_list.tmpl` (+7 -1) </details> ### 📄 Description Migrated from https://github.com/gogits/gogs/pull/3127 https://github.com/gogits/gogs/pull/3127#issuecomment-228626156 > I didn't tackle the part of the verification and I didn't have time to go further but i will re-put myself on it on the next days. Doing it in the front-end could be done easely. It just need the API to get the user public key from gogs like https://developer.github.com/v3/users/keys/. On the other hand, i don't thinks it would be too much work for the backen to do it. I have to think about it but at first at will implement the API because in both case they will be needed (or at least usefull) Closes #425 @sapk would you like to continue this by yourself? or mind filling me in on whats left to be done 🙂 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-02 11:45:50 -06:00

GiteaMirror closed this issue

2025-11-02 11:45:51 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#15406