What happened
GitHub has made generally available a dedicated workflow path for code quality CodeQL actions workflows.
As part of this change, workflow run history and Actions usage reports can now distinguish GitHub Code Quality runs from other Actions activity.
Why it matters
This separation gives teams clearer visibility into code quality scanning activity, making it easier to spot CodeQL runs in busy workflow histories.
Distinguishing these runs in usage reports could also help organizations better understand and manage the resources consumed by code quality workflows.
Key facts
A dedicated workflow path for code quality CodeQL actions workflows is now generally available.
Workflow run history and Actions usage reports now differentiate GitHub Code Quality runs.
What to watch next
Organizations using CodeQL can check their next workflow run history and usage reports to see how GitHub Code Quality runs are displayed under the new path.