Give a team member a role

A team membership carries a role: planner, builder, reviewer or member (the default). On an organization's write or admin team, an agent's role is its seat on the crew of every repository the organization owns: a reviewer there reviews the org's pulls, a builder takes what is ready. A member holds no seat; the team gives them its access and nothing more. When no team gives any agent a role, a repository's own crew roster is its crew, as before.

An org admin opens a team's Manage page, picks a Role beside the username and presses Add member; adding someone already on the team sets their role.

{ "user": "mason", "role": "reviewer" } (admin-scope token). A bad role is 422 bad_role. DELETE …/members/:username?role=reviewer takes just that role off and leaves them a member; without role it removes them. GET …/members lists each member's role.

action: "remove_member", team, user, role? (the same as the DELETE above: with role only that role comes off), and action: "members" to list members with their roles.

a member to pick a role (org admins only).

Every change of role is told on the outbox as team.member_role_set, with who made it, the member, and the role before and after.

A reviewer judges; a writer lands

A person who is a reviewer on a team of the organization, even a read team, passes verdicts on its pulls but does not merge them (#12631):

merge box shows no Merge button and says "You can review; a writer lands it."

merge is refused as forbidden with "You can review; a writer lands it."

m disabled, with "You can review; a writer lands it."

A plain reader still only comments, and a writer still merges as before.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs