NewsBite analysis · Programming, Tools · Software Release
GitHub Blog
Separate GitHub Actions path for GitHub Code Quality
GitHub has made a significant update by introducing a distinct workflow path for GitHub Code Quality CodeQL actions, which is now generally available. This change separates Code Quality runs from code scanning runs, allowing for clearer usage reports and workflow history without requiring any reconfiguration from existing users. However, developers with any dependencies on the old path or actor will need to make updates accordingly. This new streamline is designed to facilitate better tracking and reporting for GitHub users, particularly those on GitHub Enterprise Cloud and GitHub Team.
Act nowConfidence: HighImmediate horizon
Published 20 Aug 2026, 15:45 UTC1 min read
Visit original article ↗Lead image — GitHub Blog
Summary
TL;DR
- Introduces a dedicated GitHub Actions path for Code Quality.
- Allows separation of Code Quality runs from code scanning.
- No reconfiguration needed for Code Quality analysis.
- Available for GitHub Enterprise Cloud and GitHub Team.
- Users must update any built systems on the old paths.
Interesting facts
- Code Quality actions now use github-code-quality as the actor.
- This update simplifies GitHub usage reports for developers.
- Emphasizes GitHub's commitment to enhancing developer workflows.