proposal: API for querying collaborator permissions #6980

New Issue

GiteaMirror · 2025-11-02T07:12:46-06:00

GiteaMirror commented

2025-11-02 07:12:46 -06:00

Originally created by @nome on GitHub (Mar 9, 2021).

Gitea version (or commit ref): 1.13.4
Git version: N/A
Operating system: Linux (Official Docker Image)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL) https://try.gitea.io/org/collab_perms/teams/users
- No
Log gist:

Description

Context: I have defined a team with can_create_org_repo and write permission to all repos. Team members are considered maintainers/contacts for the repositories they have admin privileges on. Now I want other members of the same team to be able to query (via a custom client) the admin(s) of a given repo.

In the GitHub API, GET /repos/{owner}/{repo}/collaborators returns the permissions of each collaborator along with the user info, e.g. "permissions": { "pull": true, "push": true, "admin": false }. I think this would be the preferred way of implementing this feature.

Possible alternatives:

GET /repos/{owner}/{repo}/collaborators/{username}/permission - less efficient in this use case, because it would require multiple requests
Filter collaborators returned in GET /repos/{owner}/{repo}/collaborators by their permissions using an optional parameter - would deviate from the GitHub API
Add a separate endpoint, e.g. GET /repos/{owner}/{repo}/permissions for querying collaborator permissions - would deviate from the GitHub API

Screenshots

Originally created by @nome on GitHub (Mar 9, 2021).   - Gitea version (or commit ref): 1.13.4 - Git version: N/A - Operating system: Linux (Official Docker Image)    - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://try.gitea.io/org/collab_perms/teams/users - [ ] No - Log gist:    ## Description  Context: I have defined a team with `can_create_org_repo` and write permission to all repos. Team members are considered maintainers/contacts for the repositories they have admin privileges on. Now I want other members of the same team to be able to query (via a custom client) the admin(s) of a given repo. In the GitHub API, [`GET /repos/{owner}/{repo}/collaborators`](https://docs.github.com/en/rest/reference/repos#list-repository-collaborators) returns the permissions of each collaborator along with the user info, e.g. `"permissions": { "pull": true, "push": true, "admin": false }`. I think this would be the preferred way of implementing this feature. Possible alternatives: * [`GET /repos/{owner}/{repo}/collaborators/{username}/permission`](https://docs.github.com/en/rest/reference/repos#get-repository-permissions-for-a-user) - less efficient in this use case, because it would require multiple requests * Filter collaborators returned in `GET /repos/{owner}/{repo}/collaborators` by their permissions using an optional parameter - would deviate from the GitHub API * Add a separate endpoint, e.g. `GET /repos/{owner}/{repo}/permissions` for querying collaborator permissions - would deviate from the GitHub API ## Screenshots

GiteaMirror added the type/proposal modifies/api labels 2025-11-02 07:12:46 -06:00

GiteaMirror closed this issue

2025-11-02 07:12:46 -06:00

GiteaMirror commented

2025-11-02 07:12:46 -06:00

@Greg-NetDuma commented on GitHub (Mar 10, 2021):

GET /repos/{owner}/{repo}/collaborators/{collaborator} currently returns an empty response, it could return the permissions for that user if the user is a collaborator.

@Greg-NetDuma commented on GitHub (Mar 10, 2021): `GET /repos/{owner}/{repo}/collaborators/{collaborator}` currently returns an empty response, it could return the permissions for that user if the user is a collaborator.

GiteaMirror commented

2025-11-02 07:12:47 -06:00

@zeripath commented on GitHub (Mar 11, 2021):

lol this was one of my first prs that was rejected as it changed the api...

@zeripath commented on GitHub (Mar 11, 2021): lol this was one of my first prs that was rejected as it changed the api...

GiteaMirror commented

2025-11-02 07:12:47 -06:00

@6543 commented on GitHub (Apr 29, 2022):

-> #18761

@6543 commented on GitHub (Apr 29, 2022): -> #18761

Sign in to join this conversation.