GitHub has introduced a dedicated workflow path for GitHub Code Quality, separating it from code scanning in Actions usage reports and run history. This change is now generally available.
Previously, Code Quality analysis ran on the dynamic/github-code-scanning/codeql path and used the github-advanced-security actor, sharing resources with GitHub code scanning. Under the new configuration, Code Quality analysis runs on dynamic/github-code-quality/codeql and identifies itself with the github-code-quality actor.
This separation allows users to distinguish Code Quality runs from code scanning runs in their workflow run history and billing reports.
Required Actions
Code Quality does not require reconfiguration. Existing enabled repositories continue to function as expected. However, users who have built dashboards, scripts, or workflow run filters based on the old path or actor must update them:
- Update Actions usage and billing reports to filter on
dynamic/github-code-quality/codeqlin addition to the previousdynamic/github-code-scanning/codeqlpath. - Update scripts, dashboards, or workflow run filters that identify Code Quality runs by the
github-advanced-securityactor.
This feature is available on GitHub Enterprise Cloud, GitHub Team, and GitHub Enterprise Cloud with data residency.