Code scanning adds a mitigated alert dismissal reason
GitHub has updated its code scanning feature to include a new alert dismissal reason: "mitigated." This addition allows developers to specify that an alert was dismissed because the underlying issue has been mitigated, rather than using a more generic reason. The change is documented in the GitHub Changelog entry titled "Code scanning adds a mitigated alert dismissal reason," published on August 20, 2026. The new dismissal reason provides a clearer audit trail for security alerts, helping teams communicate why an alert was closed. This update is part of GitHub's continuous enhancement of its code scanning capabilities, which are used to identify security vulnerabilities in code. The changelog entry does not provide additional details about the implementation or any related changes, but the addition of a specific dismissal reason is a straightforward improvement to the alert management workflow.
Developers can now more accurately record why a code scanning alert was dismissed, improving audit trails.