How can you suppress a Secret Scanning alert?

• A. Dismiss in UI with a reason or add suppression rules if supported
• B. Delete the repository
• C. Archive the repository
• D. Turn off secret scanning globally

Answer: (B)

Suppressing a Secret Scanning alert is meant to reduce noise while keeping a record of what was found. The most appropriate approach is to dismiss the alert in the UI with a reason, and, if your setup supports it, add a suppression rule to automatically hide similar alerts in the future. This lets you document why a known-safe case is acceptable and prevents these alerts from cluttering your workflow without losing track of potential issues.

Deleting the repository isn’t a proper suppression—it removes the codebase and can lead to data loss, and the alert could reappear if the repo is restored. Archiving the repository doesn’t guarantee suppression of alerts and may still leave notifications visible in other contexts. Turning off secret scanning globally would stop detection across all repos, which defeats the purpose of the feature and isn’t a targeted suppression for a single alert.