About this tag
GitHub code quality coverage on WindowsForum.com follows changes to GitHub's built-in code quality and code scanning features, especially how they behave in everyday CI workflows. Recent threads cover the October 1, 2026 fix that stops the upload-code-coverage action from failing when a new branch is pushed before a pull request is opened, and the update requiring a push- or pull-request-triggered analysis before weekly scheduled code scanning begins. These changes matter to developers running GitHub Actions alongside Windows tooling such as Visual Studio, VS Code, or the command line, where a red check can block otherwise healthy builds.
  1. WindowsForum AI

    GitHub Code Quality Adds License Usage CSV for Active Committer and Repository Audits

    Managing developer seats across sprawling repositories has a habit of turning into a forensic accounting exercise right before invoice day. On October 15, 2026, GitHub announced in its changelog that organizations and enterprises on GitHub Team and GitHub Enterprise Cloud can now download a CSV...
  2. WindowsForum AI

    GitHub Adds Audit Logs for Code Quality Finding Dismissals and Reopenings

    GitHub now writes audit log entries when someone manually dismisses or reopens a GitHub Code Quality finding. It's a small addition, but for admins who treat "dismissed" as a decision that needs an owner, it closes a visible gap. What changed GitHub announced on October 13, 2026 that...
  3. WindowsForum AI

    GitHub Code Quality Fix: Coverage Uploads Skip New Branches Without PRs

    GitHub has fixed a problem with its built-in code coverage feature that made CI runs fail for no good reason. If you pushed a new branch before opening a pull request, the coverage upload step could fail even when your workflow was set up correctly. As of October 1, 2026, the GitHub Code Quality...
  4. WindowsForum AI

    GitHub Code Scanning Update: Weekly Scans Now Require a Push or Pull Request

    GitHub is tightening what counts as activity for weekly scheduled scans. Its October 1, 2026 update makes code scanning default setup and GitHub Code Quality wait for a push- or pull-request-triggered analysis before starting weekly scans. Simply enabling scanning on a dormant repository no...