Coding Tools
GitHub Introduces Separate Path for Code Quality
GitHub Changeloghigh confidence
Why it matters
- →Separating code quality from code scanning improves workflow management.
- →Developers gain clearer insights into their code quality processes.
- →The update enhances GitHub's toolset for enterprise and team users.
GitHub has launched a separate workflow path for its CodeQL actions, specifically for code quality analysis. This change allows users to differentiate between code quality and code scanning runs in their workflow histories and usage reports. While existing setups remain unaffected, users who have customized scripts or reports based on the previous path need to make updates. This update is available on GitHub Enterprise Cloud and GitHub Team, providing clearer management for developers.
Read originalThe story around this
Earlier coverage that leads up to this article, and what followed. Lines connect each piece to the closest one after it, converging here.
How we got here
- 1GitHub Code Quality Now Generally Available
GitHub Changelog · July 20, 2026 · Same story
- 2GitHub Enhances Code Scanning Customization
GitHub Changelog · August 4, 2026 · Related
More in Coding Tools
Coding Toolscoding
Claude Code v2.1.316: Subagents and Gateway Budgets
Anthropic is tightening control over Claude Code's autonomous behavior with new environment variables that let you disable 'ultrathink' or cap subagent effort levels. For teams, the introduction of pooled group budgets on the gateway allows shared monthly spending limits across members, a practical fix for enterprise cost management. The release also patches critical bugs where shell commands would hang or crash on exit, stabilizing the developer experience significantly.
Claude Code Releases
Coding Toolscoding
llama.cpp b12022 adds ROCm 10 and Snapdragon support
This release quietly cements llama.cpp as the universal inference runtime by finally bringing ROCm 10.0 to Linux and Windows alongside CUDA 13.4, effectively closing the hardware gap for AMD users who were previously left behind. The inclusion of native Snapdragon support on Linux marks a significant step toward running local LLMs on ARM-based mobile chips without emulation overhead. While KleidiAI on Apple Silicon is disabled in this build, the broader expansion to diverse accelerators ensures that developers aren't locked into NVIDIA ecosystems anymore.