--- title: Separate GitHub Actions path for GitHub Code Quality description: GitHub Code Quality now runs its CodeQL analysis on a separate Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named... canonical: https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Separate GitHub Actions path for GitHub Code Quality | daily.dev og:description: GitHub Code Quality now runs its CodeQL analysis on a separate Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named... og:url: https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko og:image: https://api.daily.dev/og/posts/Oy78Rv6kO.png og:image:alt: Separate GitHub Actions path for GitHub Code Quality og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Separate GitHub Actions path for GitHub Code Quality **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 1 min read · 0 upvotes · 0 comments ## Summary GitHub Code Quality now runs its CodeQL analysis on a separate Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named github-code-quality, instead of sharing the dynamic/github-code-scanning/codeql path and github-advanced-security actor used by code scanning. Enabled repositories keep working without changes, but any scripts, dashboards, billing reports, or workflow filters that identify Code Quality runs by the old path or actor need to be updated to also account for the new ones. GitHub Code Quality is available on GitHub Enterprise Cloud, GitHub Team, and GitHub Enterprise Cloud with data residency. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why did my GitHub Actions usage report suddenly stop showing GitHub Code Quality runs under github-advanced-security? GitHub Code Quality now runs on its own dedicated Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named github-code-quality, separate from the dynamic/github-code-scanning/codeql path and github-advanced-security actor used by code scanning. Any billing reports, dashboards, or scripts filtering on the old path or actor need to be updated to also include the new ones. _daily.dev surfaces changes like this so CI dashboards and billing filters don't quietly break._ ### Do I need to reconfigure GitHub Code Quality after the new Actions workflow path rollout? No, GitHub Code Quality itself does not need reconfiguration and enabled repositories continue scanning as before. Only external artifacts built on the old path or actor, such as usage reports, billing filters, dashboards, and workflow run filters referencing dynamic/github-code-scanning/codeql or the github-advanced-security actor, need updating to also recognize dynamic/github-code-quality/codeql and github-code-quality. _Track GitHub Actions changes like this on daily.dev before they break your automation._ ## Similar posts on daily.dev - [GitHub Code Quality is now generally available](https://daily.dev/posts/github-code-quality-is-now-generally-available-zpwhouccy) · GitHub Changelog · 7 upvotes · 1 comments - [GitHub Code Quality enterprise policy](https://daily.dev/posts/github-code-quality-enterprise-policy-lwyraqlud) · GitHub Changelog · 0 upvotes · 0 comments - [GitHub Code Quality Moves to General Availability, Bringing New Costs and Capabilities](https://daily.dev/posts/github-code-quality-moves-to-general-availability-bringing-new-costs-and-capabilities-sbbd48dzp) · DevOps.com · 1 upvotes · 0 comments - [CodeQL 2.26.4 improves GitHub actions security detections](https://daily.dev/posts/codeql-2-26-4-improves-github-actions-security-detections-2xug4do8x) · GitHub Changelog · 0 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#github-actions](https://daily.dev/tags/github-actions), [#codeql](https://daily.dev/tags/codeql) [View this post on daily.dev](https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Separate GitHub Actions path for GitHub Code Quality","url":"https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko"},"datePublished":"2026-08-20T15:11:49.667Z","dateModified":"2026-08-20T15:12:09.723Z","description":"GitHub Code Quality now runs its CodeQL analysis on a separate Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bbc9ac9f4fed15ea6eaffc05d3c5cfa9?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bbc9ac9f4fed15ea6eaffc05d3c5cfa9?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cicd,github-actions,codeql","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Separate GitHub Actions path for GitHub Code Quality"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/separate-github-actions-path-for-github-code-quality-oy78rv6ko#faq","mainEntity":[{"@type":"Question","name":"Why did my GitHub Actions usage report suddenly stop showing GitHub Code Quality runs under github-advanced-security?","acceptedAnswer":{"@type":"Answer","text":"GitHub Code Quality now runs on its own dedicated Actions workflow path, dynamic/github-code-quality/codeql, with a distinct actor named github-code-quality, separate from the dynamic/github-code-scanning/codeql path and github-advanced-security actor used by code scanning. Any billing reports, dashboards, or scripts filtering on the old path or actor need to be updated to also include the new ones. daily.dev surfaces changes like this so CI dashboards and billing filters don't quietly break."}},{"@type":"Question","name":"Do I need to reconfigure GitHub Code Quality after the new Actions workflow path rollout?","acceptedAnswer":{"@type":"Answer","text":"No, GitHub Code Quality itself does not need reconfiguration and enabled repositories continue scanning as before. Only external artifacts built on the old path or actor, such as usage reports, billing filters, dashboards, and workflow run filters referencing dynamic/github-code-scanning/codeql or the github-advanced-security actor, need updating to also recognize dynamic/github-code-quality/codeql and github-code-quality. Track GitHub Actions changes like this on daily.dev before they break your automation."}}]} ```