Skip to content
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.

Changes handling collaborators #69

Closed
2 tasks done
mpsonntag opened this issue Dec 13, 2016 · 1 comment
Closed
2 tasks done

Changes handling collaborators #69

mpsonntag opened this issue Dec 13, 2016 · 1 comment
Assignees

Comments

@mpsonntag
Copy link
Contributor

mpsonntag commented Dec 13, 2016

Currently collaborators are added with repository permission level can-push which cannot be changed.

  • Add PUT route /users/{user}/repos/{repo}/collaborators/{username}/permission to update the repository permission level of a collaborator. The user facilitating this change has to at least have the is-admin repo access level for the repository in question. Only valid store.repo.AccessLevel are supported.
  • Edit listRepoCollaborators to include the repository permission level of a collaborator to the response JSON.
@mpsonntag
Copy link
Contributor Author

putRepoCollaborator basically already does exactly what is required to update the repository permission level of a collaborator. Instead of creating yet another route it would be best to just use this for both creating a new collaborator and updating the access level of an existing one.

@mpsonntag mpsonntag self-assigned this Jan 13, 2017
@gicmo gicmo closed this as completed in #71 Jan 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant