VS Code Copilot "Co-Authored-by" Commit Controversy: Everything You Need to Know

Published: 2026-05-04 · 7 min read

The short version: Microsoft merged a PR that enables automatic "Co-authored-by: Copilot <copilot@github.com>" trailers on all git commits by default — regardless of whether Copilot was actually used. The backlash was immediate: 1,458 points and 805 comments on Hacker News, the PR was locked, then reverted. Here's the full story.

What Happened?

On April 29, 2026, VS Code engineer cwebster-99 opened PR #310226 with a seemingly small change: flip the default of git.addAICoAuthor from "off" to "all".

That single line changed the default behavior of VS Code's Git extension so that every commit would include:

Co-authored-by: Copilot <copilot@github.com>

The trailer was supposed to be added "when AI-generated code contributions are detected" — but in practice, the detection was aggressive enough that it triggered on most commits. The PR description:

"This PR changes the Git extension's git.addAICoAuthor setting so that AI co-author trailers are enabled by default, making the default behavior automatically add a Co-authored-by trailer when AI-generated code contributions are detected."

The Backlash

The developer community reacted immediately and loudly. The story hit #1 on Hacker News with 1,458 points and over 800 comments — one of the most active threads of the week.

Key criticisms included:

The thread on Hacker News was a mix of anger, satire ("Copilot also contributed to my coffee this morning"), and genuine concern about Microsoft's approach to AI tooling.

What Actually Got Merged?

Despite the backlash, the PR was merged — but the controversy didn't end there. The change shipped in an insider build, and the community's reaction forced Microsoft to reassess.

Microsoft then locked the PR as spam and limited conversation to collaborators, which was widely seen as a poor response to legitimate community feedback.

As of May 2, the git.addAICoAuthor default change remains in the codebase but several downstream discussions are ongoing about whether to:

Why Developers Are Actually Upset

On the surface, this looks like a small config change. But it touches a deeper nerve:

1. Trust in tooling

Developers rely on git history as an accurate record of who wrote what. When a tool silently adds attribution metadata, it breaks that trust. If you can't trust your commit log, what can you trust?

2. AI credit inflation

There's already debate about how much code generated by AI should be credited. Auto-attaching "Co-authored-by: Copilot" to every commit inflates AI's role and devalues human contribution.

3. The opt-out trap

Most developers never check their Git extension settings. A default change means millions of VS Code users would unknowingly have this enabled. Dark patterns in developer tools are especially galling because developers build tools and know better.

4. Licensing gray area

While "Co-authored-by" isn't legally binding in most contexts, some open source projects have specific contribution guidelines. An automated bot-persona being listed as a co-author creates confusion around DCO (Developer Certificate of Origin) and copyright assignments.

How to Check If You're Affected

If you use VS Code with the Git extension, here's how to check your setting:

# Open VS Code settings
# Search for: git.addAICoAuthor
# If value is "all" or not set, then Copilot trailers are being added
# To disable:
# Set git.addAICoAuthor to "off"

Or in your settings.json:

{
  "git.addAICoAuthor": "off"
}

The Broader Context: AI Attribution in 2026

This controversy isn't happening in a vacuum. 2026 has seen several related debates:

The VS Code PR is a microcosm of these larger questions. The tech industry is grappling with how to properly attribute AI contributions — and doing it badly erodes trust.

What We Can Learn From This

  1. Default settings matter. The difference between opt-in and opt-out can be the difference between acceptance and outrage.
  2. Don't mess with git history. Git is the canonical record of software development. Anything that pollutes it needs extreme care.
  3. Listen to feedback. Locking the PR and limiting conversation only made the situation worse. Microsoft would have been better served by acknowledging concerns and rolling back.
  4. AI attribution is hard. We need community standards for how and when to credit AI tools. This isn't the last controversy we'll see.

The Latest (May 4, 2026)

As of this writing, the PR remains merged but locked. The Hacker News thread is still active. Multiple VS Code issue threads are tracking the fallout. The community is watching to see if Microsoft will revert in a stable release or double down.

If you care about this issue, the best thing to do is:

Update (May 4): Following the backlash, reports indicate Microsoft is reconsidering the default value internally. Expect a follow-up PR or setting clarification in the coming days.

FAQ

Does this affect GitHub.com or just VS Code?

This change is specific to VS Code's Git extension. GitHub.com doesn't have this behavior — yet.

Does the trailer affect DCO or CLA checks?

It can. Some CI/CD pipelines check "Co-authored-by" trailers as part of contribution validation. False positives can block PRs.

Was the PR reverted?

Not as of May 4. The PR is merged but locked. The setting default remains "all" in insider builds. Community pressure is building for a revert.

Should I disable it?

If you don't want Copilot automatically credited in your commits, add "git.addAICoAuthor": "off" to your settings.json. If you do use Copilot and want proper attribution, consider the new GitHub Copilot dashboard for tracking AI contributions separate from git metadata.

Tags: VS Code, Copilot, Microsoft, git, commit attribution, AI, developer controversy, PR #310226, Co-authored-by, Hacker News

First published: 2026-05-04 · Last updated: 2026-05-04
Hacker News discussion (1,458 pts)