AZ-400 ยท Identity, access and permissions
Repository roles in a GitHub organization
Organization and repository roles (read, triage, write, maintain, admin), custom roles, teams, outside collaborators, rulesets and environment protection access.
Key points
- Read: view and discuss. Triage: manage issues and PRs, no write access.
- Write: push code, merge PRs, handle alerts.
- Maintain: day-to-day running, no destructive or security-admin actions.
- Admin: full control: branch protection, rulesets, deploy keys, webhooks, visibility, deletion.
- Organization owners: admins everywhere. Custom repository roles: GitHub Enterprise Cloud only.
- Prefer teams; outside collaborator for non-members.
Practice questions
Which is the lowest repository role that lets a person push code and merge pull requests?
- Read
- Triage
- Write
- Maintain
Show answer
Answer: C. Write
Write is intended for people who actively push changes and can merge pull requests. Read and Triage cannot push code.
Which actions need the Admin role and are not available to Maintain?
- Configuring branch protection rules and rulesets
- Managing deploy keys and webhooks
- Deleting the repository
- Merging a pull request
- Configuring allowed merge methods
Show answer
Answer: A. Configuring branch protection rules and rulesets, B. Managing deploy keys and webhooks, C. Deleting the repository
Branch protection rules and rulesets, deploy keys and webhooks, and deleting the repository are admin territory. Merging pull requests needs only Write, and Maintain can already configure merge options.
Custom repository roles are available to every organization, including those on the free plan.
Show answer
Answer: False
False. Per the roles documentation, custom repository roles are available only to organizations on GitHub Enterprise Cloud.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
