github GitHub Changelog ·

Dedicated GitHub Actions Path for Code Quality is Generally Available

securitygaengineer
feature

GitHub Code Quality now features a dedicated workflow path for CodeQL actions, distinguishing its runs from GitHub Code Scanning in workflow history and usage reports. This enhancement provides clearer visibility into Code Quality analysis activities and improved reporting accuracy. While the core Code Quality functionality remains unchanged, users must update custom scripts, dashboards, or filters that relied on the previous shared path or actor. This functionality is generally available on GitHub Enterprise Cloud and GitHub Team.

  • Separate workflow path for GitHub Code Quality
  • Update custom integrations for Code Quality reports
Breaking changes (1)
  • Update custom integrations for Code Quality reports

    Users who have built custom tooling, scripts, dashboards, or workflow run filters that rely on the previous shared path (`dynamic/github-code-scanning/codeql`) or actor (`github-advanced-security`) for Code Quality runs must update them to account for the new dedicated path and actor.

Features (1)
  • Separate workflow path for GitHub Code Quality

    GitHub Code Quality CodeQL actions now operate on a dedicated workflow path (`dynamic/github-code-quality/codeql`) with its own actor (`github-code-quality`). This change allows Code Quality runs to be distinct from GitHub Code Scanning runs in workflow history and Actions usage reports, improving clarity.

Read the original announcement →

https://github.blog/changelog/2026-08-20-separate-github-actions-path-for-github-code-quality

Related releases