GH-500 · Question #35
Assuming that no custom Dependabot behavior is configured, who has the ability to merge a pull request created via Dependabot security updates?
The correct answer is D. a user who has write access to the repository. Merging a pull request - including those created by Dependabot security updates - requires Write access to the repository. This is standard GitHub permission behavior: Read access (C) only allows viewing and cloning; Write access is the minimum level needed to merge PRs. A…
Question
Assuming that no custom Dependabot behavior is configured, who has the ability to merge a pull request created via Dependabot security updates?
Options
- Aa repository member of an enterprise organization
- Ban enterprise administrator
- Ca user who has read access to the repository
- Da user who has write access to the repository
How the community answered
(19 responses)- A5% (1)
- C5% (1)
- D89% (17)
Explanation
Merging a pull request - including those created by Dependabot security updates - requires Write access to the repository. This is standard GitHub permission behavior: Read access (C) only allows viewing and cloning; Write access is the minimum level needed to merge PRs. A repository member of an enterprise organization (A) is too vague and doesn't imply Write access. Enterprise administrators (B) have administrative capabilities but merging PRs is a repository-level Write permission, not an admin privilege.
Topics
Community Discussion
No community discussion yet for this question.