Issues & PRs Extensions

Forgejo 14.x does not provide native REST API endpoints for locking or unlocking issues and pull requests. The proxy adds these endpoints and maintains lock state in-process.

Caution

Lock state is stored in-process (in memory). It resets when the proxy container restarts. This is a temporary workaround until Forgejo adds native lock support to its REST API.

Endpoints

Issues

Method	Endpoint	Description
PUT	/api/v1/repos/{owner}/{repo}/issues/{index}/lock	Lock an issue
DELETE	/api/v1/repos/{owner}/{repo}/issues/{index}/lock	Unlock an issue

Pull Requests

Method	Endpoint	Description
PUT	/api/v1/repos/{owner}/{repo}/pulls/{index}/lock	Lock a pull request
DELETE	/api/v1/repos/{owner}/{repo}/pulls/{index}/lock	Unlock a pull request

Path Parameters

Parameter	Description
owner	Repository owner (user or organisation name)
repo	Repository name
index	Issue or PR number (the #123 shown in the Forgejo UI)

Examples

# Lock issue #42
curl -X PUT -H 'Authorization: token YOUR_TOKEN' \
  'https://forgejo-proxy.hochguertel.work/api/v1/repos/myorg/myrepo/issues/42/lock'

# Unlock issue #42
curl -X DELETE -H 'Authorization: token YOUR_TOKEN' \
  'https://forgejo-proxy.hochguertel.work/api/v1/repos/myorg/myrepo/issues/42/lock'

# Lock pull request #7
curl -X PUT -H 'Authorization: token YOUR_TOKEN' \
  'https://forgejo-proxy.hochguertel.work/api/v1/repos/myorg/myrepo/pulls/7/lock'

Response

Both PUT and DELETE return 204 No Content on success, matching Forgejo’s conventional response for state-change operations.