tag: Code-Quality · 6 items
- Platform/SRE — Skip
- CI/CD — Plan: If you use CodeQL in GitHub Actions, evaluate adopting the new dedicated workflow path to improve run-history clarity and accurate usage reporting — no deadline, but worth scheduling as routine pipeline hygiene.
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: The new Trends tab surfaces org-wide code quality movement over time rather than a point-in-time snapshot, which could inform how leaders set and track quality standards across teams — no decision required, but useful context for platform strategy reviews.
- Platform/SRE — Skip
- CI/CD — Learn: Teams using GitHub Code Quality should check whether existing rulesets that auto-requested Copilot reviews are still in place or have been silently removed; review PR workflow expectations accordingly.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Learn: GitHub now offers AI-generated coverage workflow setup from repository Code Quality settings, reducing onboarding friction; worth evaluating if teams struggle to bootstrap coverage, but no pipeline migration is required.
- Leader — Skip
- Platform/SRE — Skip
- CI/CD — Plan: New GA GitHub feature worth evaluating for pipeline quality gates; assess whether Code Quality checks should be integrated into existing GitHub Actions workflows this quarter.
- Leader — Learn: GA release of a GitHub-native code quality tool that may reduce the need for third-party static analysis seats; worth tracking as a build-vs-buy data point at next toolchain review.
- Signals: GA announcement
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: Pre-GA feature that surfaces active-committer counts to estimate Code Quality licensing costs; worth monitoring as it approaches GA before making any GitHub Advanced Security / Code Quality budget decisions.
- Signals: pre-GA (alpha/beta/RC/preview)