Share with your CTO
GitHub flipped the billing switch on Code Quality at midnight, and the more than 10,000 enterprise teams that used the free preview without disabling it are now accruing charges with no grace period and no confirmation prompt. The structure is three cost lines, not one: $10 per active committer per month for the base license, variable AI Credits at $0.01 each for Copilot-powered review and Autofix, and standard GitHub Actions compute minutes for every CodeQL scan. GitHub’s 90-day committer window means the billable headcount is almost certainly larger than the team actively working on any enabled repository today.
What this means for your business
The committer definition is where this gets expensive fast. Anyone who pushed a commit to a Code Quality-enabled repository in the last 90 days counts, including contractors who wrapped up a project in April, external collaborators, and pending invitees. For organizations that enabled Code Quality broadly across monorepos during the preview period, which was rational when it cost nothing, the billing headcount can easily run 30 to 50 percent above the current active engineering team. Pull the actual number from the billing settings before rationalizing scope.
GitHub’s pricing architecture here is the same pattern that generated nearly 1,000 downvotes on the Copilot AI Credits announcement in June: a predictable base fee layered with open-ended metered costs for anything touching a model. The base fee is budgetable. The AI usage line is not, unless a hard spending cap is set before the first billing cycle closes. Teams running high-frequency pull request flows with Copilot Autofix enabled will discover this the same way Copilot power users discovered 10x to 50x cost increases after the June 1 model transition. There is no model-switching option to reduce AI credit consumption in Code Quality.
The question worth holding: does Code Quality’s native GitHub integration justify the cost against an incumbent like SonarQube, which prices on lines of code rather than committers? For large, active teams on smaller codebases, SonarQube’s model almost certainly wins on unit economics. For teams with broad contributor bases and deep GitHub Enterprise Cloud entanglement, the integration advantage of avoiding a third-party vendor relationship is real but needs to be priced, not assumed. Run the comparison before the first invoice arrives, not after.
Concept deep-dive: Active committer billing windows
GitHub’s 90-day active committer window determines who is billable by scanning push history, not current org membership. The window rolls forward with the billing period, meaning a single commit in April still generates a billable seat through mid-July. This exists because static analysis tools derive value from the full contributor footprint of a codebase, not just whoever is merged today. Think of it like a concert venue charging based on peak occupancy, not the number of people still in their seats at closing. The practical implication: scope decisions made during free preview periods have a billing tail that outlasts the decision itself.
Based on reporting from GitHub Code Quality Billing Starts Today: What 10,000 Enterprise Teams Must Audit Now, originally published 2026-07-20 06:27:00.
