What happened
GitHub Code Quality has expanded its audit logging to record every time someone enables, disables, or adjusts its settings on a repository. This means configuration changes are no longer silent.
The history is captured through three new events, including repo.code_quality_enabled, which records when the feature is turned on. The other two events cover the remaining enablement and settings actions.
Why it matters
For organizations that rely on audit logs for security and compliance, this change offers a clearer view of how Code Quality is being configured across repositories. It makes it easier to spot unexpected modifications or verify that changes follow internal policy.
Previously, such configuration activity may have left no trace in the audit trail. Now admins have a documented record of who changed Code Quality settings and when.
Key facts
GitHub Code Quality writes an audit log event whenever someone enables, disables, or changes its settings on a repository.
Three new events provide this history.
One of the new events is repo.code_quality_enabled.
What to watch next
Teams should check whether their audit log monitoring and alerting systems capture these new events, especially if they track configuration changes closely.
It may also be useful to establish internal review processes for unexpected Code Quality setting changes, now that they leave an audit trail.