Who can fix a code scanning alert on a private repository?

The correct answer is B. users who have Write access to the repository. Fixing a code scanning alert requires Write access to the repository because it involves making code changes (editing files and pushing commits) to remediate the vulnerability. Users with only Read access (D) can view alerts but cannot push fixes. Users with the Triage role (C)…

Best Practices and Remediation

Question

Options

Ausers who have the security manager role within the repository
Busers who have Write access to the repository
Cusers who have the Triage role within the repository
Dusers who have Read permissions within the repository

How the community answered

(25 responses)

A
4% (1)
B
92% (23)
D
4% (1)

Explanation

Fixing a code scanning alert requires Write access to the repository because it involves making code changes (editing files and pushing commits) to remediate the vulnerability. Users with only Read access (D) can view alerts but cannot push fixes. Users with the Triage role (C) can manage alerts (dismiss, comment) but cannot write code changes. The security manager role (A) grants visibility into security alerts across an organization but does not by itself grant the ability to push code to a private repository.

Topics

#Code Scanning Alerts#Repository Permissions#Alert Remediation#GitHub Roles

Community Discussion

No community discussion yet for this question.

Full GH-500 Practice