Lesson231 words

Permissions and roles in GitHub

Design and implement permissions and roles in GitHub

Repository roles

RoleCan
ReadPull, view and discuss, and open issues
TriageManage issues, discussions, and pull requests without write access
WriteActively push changes, subject to branch/ruleset controls
MaintainManage the repository without sensitive or destructive actions
AdminFull repository access, including sensitive/destructive actions

These are GitHub's five standard organization-repository roles; Enterprise Cloud can also define custom roles. Choose the least-privileged role that fits the work.

Teams

Prefer teams for reusable organization-member access and lifecycle management. Direct person grants remain supported. A child team inherits its parent team's repository access, so every parent grant must be safe for all child-team members.

Outside collaborators

An outside collaborator is not an organization member and receives a chosen role on specific repositories. Outside collaborators cannot join organization teams, and organization base permissions do not apply to them.

Branch protection and rulesets

A repository role grants baseline capabilities. Branch protection and rulesets layer on branch/tag restrictions, required reviews or checks, signed-commit or deployment requirements, and bypass controls. They can also restrict who may push, so role and rule configuration must be evaluated together.

Primary sources

Ready to study Designing and Implementing Microsoft DevOps Solutions (AZ-400)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free