Code scanning now creates alert-related events in audit log

The enterprise and organization-level audit log events are now created when a code scanning alert is created, fixed, dismissed, reopened, or appeared in a new branch:

• code_scanning.alert_created – a code scanning alert was seen for the first time;
• code_scanning.alert_appeared_in_branch – an existing code scanning alert appeared in a branch;
• code_scanning.alert_closed_became_fixed – a code scanning alert was fixed;
• code_scanning.alert_reappeared – a code scanning alert that was previously fixed reappeared;
• code_scanning.alert_closed_by_user – a code scanning alert was manually dismissed;
• code_scanning.alert_reopened_by_user – a code scanning alert that was previously dismissed was reopened.

The new functionality, which will be included in GHES 3.17, provides more insight into the history of a code scanning alert for easier troubleshooting and analysis.

For more information:

• Learn more about code scanning
• Learn more about audit log events for your enterprise
• Learn more about audit log events for your organization