Where can a user change a repository's code scanning severity threshold that fails a pull request status check?

The correct answer is C. Security tab. Code scanning configuration - including the alert severity level (e.g., Critical, High) that causes a pull request status check to fail - is managed under the repository's Security tab (specifically 'Code security and analysis' or 'Code scanning' settings). The Actions tab…

Configure and use Code Scanning with CodeQL

Question

Where can a user change a repository’s code scanning severity threshold that fails a pull request status check?

Exhibit

Options

ASettings tab
BActions tab
CSecurity tab
DPull Requests tab

How the community answered

(35 responses)

A
3% (1)
B
3% (1)
C
94% (33)

Explanation

Code scanning configuration - including the alert severity level (e.g., Critical, High) that causes a pull request status check to fail - is managed under the repository's Security tab (specifically 'Code security and analysis' or 'Code scanning' settings). The Actions tab shows workflow run logs but not security policy settings. The Settings tab houses general repository configuration, but the code scanning severity threshold is surfaced under Security, not under the top-level Settings. The Pull Requests tab has no security configuration options.

Topics

#Code scanning configuration#Severity thresholds#Pull request status checks#GitHub UI

Community Discussion

No community discussion yet for this question.

Full GH-500 Practice