GitHub Code Quality 启用独立的 GitHub Actions 路径

面向代码质量的 CodeQL Actions 工作流现已全面可用专用工作流路径。现在，你的工作流运行历史和 Actions 使用量报告可以将 GitHub Code Quality 运行与 GitHub 代码扫描运行区分开来。Code Quality 分析将在 dynamic/github-code-quality/codeql 上运行，并显示 github-code-quality 作为执行者；不再与代码扫描共用 dynamic/github-code-scanning/codeql 路径及 github-advanced-security 执行者。

Code Quality 本身无需重新配置，已启用的仓库将继续按原有方式进行扫描。如果你基于旧路径或执行者构建了任何集成，则需要进行更新：

• 更新按 dynamic/github-code-scanning/codeql 筛选的 Actions 使用量和计费报告，使其同时纳入 dynamic/github-code-quality/codeql。
• 更新通过 github-advanced-security 执行者识别 Code Quality 运行的脚本、仪表盘或工作流运行筛选器。

GitHub Code Quality 可用于 GitHub Enterprise Cloud、GitHub Team，以及支持数据驻留的 GitHub Enterprise Cloud。了解更多信息，请参阅 GitHub Code Quality 计费。

欢迎在 GitHub Community 中参与讨论。

A dedicated workflow path for code quality CodeQL actions workflows is now generally available. Your workflow run history and your Actions usage reports now tell GitHub Code Quality runs apart from GitHub code scanning runs. Code Quality analysis runs on dynamic/github-code-quality/codeql and shows github-code-quality as the actor, instead of sharing the dynamic/github-code-scanning/codeql path and the github-advanced-security actor with code scanning.

Code Quality itself doesn’t need reconfiguration, and your enabled repositories keep scanning as they are. If you’ve built anything on the old path or actor, you need to update it:

• Change Actions usage and billing reports that filter on dynamic/github-code-scanning/codeql so they also account for dynamic/github-code-quality/codeql.
• Update scripts, dashboards, or workflow run filters that identify Code Quality runs by the github-advanced-security actor.

GitHub Code Quality is available on GitHub Enterprise Cloud and GitHub Team, as well as on GitHub Enterprise Cloud with data residency. To learn more, see GitHub Code Quality billing.

Join the discussion within GitHub Community.