GitHub Adds Audit Logging for Code Quality Finding Dismissals and Reopenings

What changed?

GitHub now logs manual dismissals and reopenings of Code Quality findings in the organization and enterprise audit log. Two new audit log event types have been added: repo.code_quality_findings_dismissed and repo.code_quality_findings_reopened. Each event includes details on the requester, timestamp, affected repository and rule, and identifiers and count of findings impacted.

Why does it matter to an everyday developer?

This update enables organizations to track who is manually dismissing or reopening Code Quality issues in repositories. This improves accountability and transparency for teams where code quality is critical and can help identify patterns of mismanagement or repeated overrides. Auditing these actions is particularly important for teams in regulated environments or those enforcing strict code quality policies.

What can the developer do now?

If you use GitHub Team or Enterprise Cloud, you can filter your organization or enterprise audit log, or query the audit log API, for the new repo.code_quality_findings_dismissed and repo.code_quality_findings_reopened events. No additional setup is needed if Code Quality is already enabled. Developers and administrators can use these logs to review activity around code quality backlog findings. Note that this feature is not available on GitHub Enterprise Server.