VS Code is Sneaking Copilot Credits Into Your Git Commits

Microsoft's VS Code just got caught red-handed. Developers are reporting that their editor is automatically adding "Co-Authored-by: GitHub Copilot" to git commits. The kicker? Many of these developers never even used Copilot to write the code.

This isn't just a bug. It's a fundamental breach of trust that affects every developer using VS Code. Your commit history is sacred. It's the permanent record of who built what. And now Microsoft is polluting it with AI marketing.

What's Actually Happening

VS Code has been quietly inserting co-author credits for GitHub Copilot into git commit messages. The problem isn't that it credits AI when you use it. The problem is that it's doing this even when Copilot had zero involvement in writing the code.

Developers on Hacker News are sharing screenshots of commits where they wrote everything by hand, yet Copilot gets credited as a co-author. Some report this happening on code they wrote months ago, before they even had Copilot installed.

The feature appears to be tied to VS Code's git integration and Copilot extension. When both are active, the editor makes assumptions about AI involvement that simply aren't true.

Why This Matters Beyond Developer Drama

Your git history isn't just metadata. It's legal evidence.

In corporate environments, commit authorship determines intellectual property ownership. If you're working on proprietary code and Copilot gets credited as a co-author, you've just created a paper trail suggesting AI was involved in creating your company's IP. Legal departments hate this.

For open source projects, false co-authorship credits mess with contribution tracking. GitHub's insights, contributor graphs, and project statistics all get skewed. Maintainers use this data to make decisions about project direction and contributor recognition.

Then there's the personal angle. Your commit history is your professional portfolio. It shows what you've built, when you built it, and how you work. Having AI falsely credited in your commits dilutes your actual contributions.

The Real Problem With AI Transparency

Microsoft keeps pushing the narrative that AI assistance should be transparent and credited. Fine. But transparency works both ways.

If you're going to credit AI when it helps, you need to be absolutely certain it actually helped. Auto-crediting AI for human work isn't transparency. It's false advertising.

This also reveals Microsoft's deeper strategy. By normalizing AI co-authorship in git commits, they're conditioning developers to accept AI as a standard part of the development process. Every commit with a Copilot credit becomes a tiny advertisement for their AI tools.

The goal isn't accurate attribution. It's market conditioning.

How to Fix This Right Now

First, check your recent commits. Look for any "Co-Authored-by: GitHub Copilot" lines you didn't add manually. If you find them, you know you're affected.

To stop this from happening:

  1. Disable the setting: Open VS Code settings and search for "copilot commit". Turn off any auto-attribution features you find.

  2. Review your extensions: Check which Copilot-related extensions you have installed. Some add this behavior by default.

  3. Use git hooks: Set up a pre-commit hook that strips unwanted co-author lines from your commit messages automatically.

For existing commits, you can't easily change them without rewriting git history. But you can add clarifying commits that explain which work was actually yours.

The Bigger Picture

This controversy isn't really about git commits. It's about who controls the narrative around AI in software development.

Microsoft wants developers to see AI as an inevitable, standard part of coding. By inserting Copilot credits everywhere, they normalize the idea that all code is somehow AI-assisted.

But most code is still written by humans. And humans deserve accurate credit for their work.

The solution isn't to ban AI from development. It's to demand accuracy in how we track and credit contributions. If AI helps write code, credit it. If it doesn't, don't.

Your commits should reflect reality, not Microsoft's marketing goals.

— Dolce