VS Code is silently injecting 'Co-Authored-by Copilot' into git commits regardless of whether you used it or not. The dev community is losing its mind over this.
Imagine this: It's Friday afternoon. You've just gracefully typed out a brilliant fix, staged your files, and pushed to the repo so you can go grab a beer. Boom! You check your git history and realize your commit has been hijacked by a spectral entity known as Copilot, boldly claiming co-authorship. The kicker? You didn't even use the damn thing today. Wild, right?
This exact scenario is blowing up on Hacker News right now with over 1100 points of pure developer rage. Let's break down what the hell is actually going on.
It all started with Pull Request #310226 on the VS Code GitHub repo. A sharp-eyed dev noticed a highly questionable behavior: VS Code is automatically injecting a Co-Authored-by Copilot trailer into commit messages.
Now, if you actually asked Copilot to generate the code, sure, give credit where credit is due. But NOPE! Even if you grind it out yourself, sweating over every single line of code with your bare hands, VS Code (or its extension) still sneaks that tag in. It's like cooking a gourmet meal from scratch, only to have your roommate pop into the kitchen right as you serve it and say, "We made this!"
Needless to say, the dev community is out for blood. The git history is a sacred space for engineers. Polluting it is a cardinal sin. Here are the main battle lines being drawn:
1. The Tinfoil Hat Brigade: Stat Padding Many veterans are putting on their tinfoil hats, arguing this isn't a bug—it's a feature. The theory goes that Microsoft is trying to pad their usage metrics. Imagine middle management checking GitHub and seeing "Co-Authored-by Copilot" everywhere. They'll think, "Wow, our devs are 10x-ing with AI, let's renew those expensive enterprise licenses!" It's guerrilla marketing at its worst.
2. The "Git History is Sacred" Camp
Most devs are just furious that ai tools are overstepping their boundaries. Commit data isn't just text; it dictates git blame and sometimes even performance metrics. If you didn't write the code, get out of my commit history. What happens when that code breaks production? Is the bot going to take the blame? Didn't think so.
3. The Benefit of the Doubt: "It's just a bug, chill" A smaller, more forgiving group thinks the VS Code devs just pushed some sloppy code and failed to handle the edge case where the feature is toggled off. But unfortunately, this bug hits way too close to a developer's ego to just be brushed off.
Long story short, Microsoft is going to have to push a hotfix real quick if they don't want people mass-uninstalling the extension or jumping ship to Cursor.
There's a golden rule for anyone building developer tools: Never, ever silently modify config files or mess with a user's git history without a massive, flashing confirmation prompt. We devs might be lazy, and we might copy-paste from Stack Overflow, but we are extremely territorial about our commit logs.
Go check your git log right now and see if Copilot has been secretly stealing your thunder!
Source: Hacker News - VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage
