AZ-400 Question 231
Single answerYour DevOps team is collaborating on a public GitHub repository and needs certain contributors to only review and label issues and triage pull requests, without granting them the ability to merge or push changes. Which repository role should you assign to these contributors?
- A
Triage
- B
Write
- C
Maintain
- D
Admin
Show answer and explanation
Correct answer: A
Explanation
When configuring permissions in GitHub, you can choose from predefined roles such as Read, Triage, Write, Maintain, and Admin. Triage is optimal for users who need to manage issues and pull requests without the ability to merge or push code. This makes it ideal for contributors primarily focused on quality assurance and initial review. For further details, refer to GitHub's documentation on repository roles: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/repository-roles-for-an-organization.
- A. Correct.
Correct. The Triage role grants the ability to manage issues and pull requests (e.g., labeling, closing, reopening) without the ability to merge or push changes. This aligns with the requirement to allow triaging but not merging or pushing code.
- B. Incorrect.
Incorrect. The Write role allows users to push and merge changes, which exceeds the requirement of limiting contributors to only triaging issues and pull requests.
- C. Incorrect.
Incorrect. The Maintain role allows broader repository management, including some administrative tasks such as editing repository settings, which surpasses the requirement in this scenario.
- D. Incorrect.
Incorrect. The Admin role grants full control over the repository, including adding collaborators and deleting the repository, which far exceeds the needed level of access.