Code Quality - 1

2026 (7)

October (3)

github: Download GitHub Code Quality license usage as a CSV

GitHub

2026-10-15

GitHub Code Quality now lets administrators download a CSV report of license usage to reconcile license counts with internal records. The report lists each active committer covered by the license usage data.

github: Audit GitHub Code Quality finding dismissals and reopenings

GitHub

2026-10-13

GitHub audit logs now include manual dismissals and reopenings of GitHub Code Quality findings at the organization or enterprise level. This lets admins review actions on findings that appear in a repository’s default-branch backlog or other Code Quality views.

github: Code coverage uploads no longer fail CI for new branches

GitHub

2026-10-01

GitHub Code Quality’s upload-code-coverage action no longer causes CI failures when coverage is uploaded from a branch that does not yet have an open pull request. This changes behavior from the previous failure case for new branches.

September (1)

github: Remediate Code Quality findings with agentic autofix

GitHub

2026-09-09

GitHub added agentic autofix for Code Quality findings, allowing users to select and assign up to 25 standard findings at once for automated remediation. The feature is aimed at reducing backlog items in code quality reports.

August (3)

github: Track GitHub Code Quality enablement changes in the audit log

GitHub

2026-08-20

GitHub Code Quality now emits audit log events when it is enabled, disabled, or its repository settings are changed. This adds a history trail for Code Quality configuration changes.

github: Track organization code quality trends

GitHub

2026-08-19

GitHub’s organization-level Code Quality dashboard now has a Trends tab. It shows code quality changes across repositories over time instead of only a point-in-time view.

github: Code coverage automatic enablement in Code Quality settings

GitHub

2026-08-04

GitHub added a new Code Quality setting that can automatically generate a code coverage workflow with AI. The change is meant to reduce setup time for coverage in repositories.