GitHub Separates Code Quality from Code Scanning in Actions Paths
GitHub has introduced a dedicated workflow path for GitHub Code Quality, separating it from code scanning in Actions usage reports and run history.
GitHub has introduced a dedicated workflow path for GitHub Code Quality, separating it from code scanning in Actions usage reports and run history.
GitHub Code Quality now emits audit log entries for enablement and configuration changes. This update introduces three specific events—repo.code_quality_enabled, repo.code_quality_disabled, and repo.code_quality_updated—allowing administrators to track who changed settings and when, which is critical for billing visibility regarding active committers.
GitHub has introduced a new Trends tab in the organization-level Code Quality dashboard, allowing teams to visualize changes in open findings over 7, 14, or 30-day periods and identify repositories driving quality improvements or regressions.