Summary
On October 13, 2026, GitHub introduced two audit log events that record manual dismissals and reopenings of Code Quality findings on default-branch backlogs, filterable in org and enterprise audit logs and retrievable via the audit log API on Team and Enterprise Cloud.
What changed
New audit events repo.code_quality_findings_dismissed and repo.code_quality_findings_reopened log who dismissed or reopened Code Quality backlog findings, capturing actor, timestamp, repository, rule, and affected finding IDs and count; they are filterable in org/enterprise audit logs and available via the audit log API on Enterprise Cloud (not Enterprise Server).
Why it matters
Audit trails for triage decisions give security and engineering leaders accountability over which code-quality findings get waved through, supporting compliance and reducing silent suppression of issues.
Evidence excerpt
You can now review manual dismissals and reopenings of GitHub Code Quality findings.