WayToClawEarn
High impactHacker News

VS Code controversy: Copilot automatically adds itself to Git commit records

Microsoft VS Code was exposed to automatically add Co-Authored-by Copilot tags to Git commits without the user's explicit permission. The change has been merged into the master branch, sparking strong backlash from the developer community.

WayToClawEarn EditorialPublished May 3, 2026Updated Jun 1, 2026

Editorial review of public sources · AI-assisted drafting. How we work

Core conclusion

On May 2, 2026, a post on Hacker News detonated the developer community: Microsoft VS Code automatically added a "Co-Authored-by: Copilot" tag to Git submissions without notifying users, regardless of whether the submission used Copilot. This change was merged into the main branch through PR #310226 2 weeks ago. It only changed 4 lines of code, but it triggered heated discussions about the ethics of AI tools, code ownership, and user trust.

Key Points

  • Event Time: Mid-April 2026 (PR merger) to May 2, 2026 large-scale exposure
  • Affected objects: All developers using VS Code + Git
  • Core change: Git submission records automatically add AI signatures without user operation or confirmation.
  • Community Reaction: Hacker News 583 points, 250+ comments, overwhelmingly negative

Event background

In mid-April 2026, the Microsoft VS Code team incorporated a seemingly minor change via PR #310226: enabling the default AI co-author feature. This PR was submitted by engineer cwebster-99, and only two files, extensions/git/package.json and extensions/git/src/repository.ts, were modified, with a total of 4 lines of code changes.

This change allows the Git extension of VS Code to automatically append a line Co-Authored-by: Copilot to the end of the commit message of each submission, regardless of whether the submission actually uses Copilot's code completion or conversation function. This means that even if a developer just writes purely manual code using VS Code, there will be AI-assisted records left in Git history.

Key Impact (by Dimension)

DimensionsChangeWhat it means to usRecommended actions
Code attributionGit records automatically write AI signaturesContribution records of open source projects may be contaminated by AI informationCheck whether Co-Authored-by: Copilot appears in the warehouse commit message
User trustMicrosoft directly modified the behavior without asking for user consentThe credibility of the tool has declined, and developers have become more vigilantCheck the git config related settings after updating VS Code to the latest version
Project managementThe objections of lower-level engineers are ignoredThe trust gap between management and technical layers deepensPay attention to whether subsequent updates of VS Code provide a shutdown option
Git record integrityHistorical commits are automatically markedCode review and contribution traceability may be affectedUse git log --grep to self-check the warehouse

Community reaction and controversy

On Hacker News, developer rsynnott’s comment received the most likes: One of the most fascinating aspects of the AI phenomenon is its profound hostility to standards. Whether things work or not, ethics or not, reality or not - none of it matters, the only thing that matters is please use our AI. Microsoft spent decades rebuilding its reputation, then burned it all down in worship of their robot gods.

Another upvoting comment comes from storus: This is a complete takeover by technically incompetent management. They can finally fully implement their ideas without relying on those pesky engineers with their obstructions, complaints, and questions. We will soon see managerial utopias everywhere.

Core issues in the dispute

  1. Lack of Informed Consent: The user did not receive any notification or pop-up window explaining this change
  2. Ethical issues enabled by default: Adding AI attribution to Git records changes the attribution rules for open source contributions
  3. Unable to close dilemma: Some users reported that even if the Copilot function is turned off, the mark will still appear in the submission.
  4. Authenticity of code attribution: If AI does not assist a certain submission, the AI signature is false information

代码归属争议配图

Microsoft’s response

As of the publication of this article, the Microsoft VS Code team has not officially responded to the controversy. PR #310226 has been merged, but the community is clamoring to revert the change. The PR has over 372 downvotes on GitHub (and only 2 upvotes).

It is worth noting that this is not the first time Microsoft has caused controversy over Copilot's boundary issues. Previously, GitHub Copilot has been pushed to the forefront many times due to code training data copyright issues and the risk of corporate code leakage.

Adaptation suggestions for content operators

If you use VS Code + Git to manage your website or content publishing project, the following measures can help you avoid this pitfall:

  • Check existing repository: run git log --grep="Co-Authored-by: Copilot" to see which commits have been tagged
  • Temporary workaround: Switch to the stable version of VS Code (not the Insiders version), or use another editor
  • Follow follow-up updates: Microsoft may provide a shutdown option in subsequent releases
  • Code review process: Add commit message review step before merging PR

Related extended information

Tool entry

Tool names that appear naturally in the text: VS Code, Copilot, Git, GitHub, OpenAI, ChatGPT

Internal link guidance

Disclaimer: this site shares educational insights only, for inspiration and reference. No outcome guarantee; external execution and decisions are your own responsibility.
VS Code controversy: Copilot automatically adds itself to Git commit records · WayToClawEarn