{"id":27797,"date":"2026-05-05T11:12:16","date_gmt":"2026-05-05T11:12:16","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/27797\/"},"modified":"2026-05-05T11:12:16","modified_gmt":"2026-05-05T11:12:16","slug":"typical-microsoft-turns-out-vs-code-was-adding-copilot-as-a-git-co-author-without-telling-anyone","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/27797\/","title":{"rendered":"Typical Microsoft! Turns Out VS Code Was Adding Copilot as a Git Co-Author Without Telling Anyone"},"content":{"rendered":"

\"Warp<\/a><\/p>\n

VS Code<\/a> has been quietly appending a Co-authored-by: Copilot line to users’ git commits, including ones written entirely without Copilot<\/a>‘s involvement.<\/p>\n

The culprit behind this, git.addAICoAuthor, is a feature that was introduced in VS Code 1.110<\/a> back in March. It is designed to tag commits with a Copilot co-author trailer when AI-generated code is involved, and it launched with off as the default.<\/p>\n

So far good, right? \ud83d\ude42<\/p>\n

That changed in April, when Courtney Webster<\/a>, a Product Manager at Microsoft, submitted a pull request<\/a> that changed one thing, the default value of git.addAICoAuthor from off to all<\/a>.<\/p>\n

The PR was reviewed and merged by VS Code team member Dmitriy Vasyura<\/a> on April 16, without a release note or any kind of user-facing notification.<\/p>\n

\"a<\/p>\n

The all setting is the broadest option available for git.addAICoAuthor, which added the Copilot trailer to every commit involving any AI interaction, including inline completions.<\/p>\n

With the default flipped to all, anyone who had not manually configured the setting was suddenly getting Copilot credited in their git history.<\/p>\n

Things got messier from there. Developers reported<\/a> that the credit info (trailer) was appearing even with chat.disableAIFeatures set to true. The trailer<\/a> is also appended after the commit finalizes, not appearing in VS Code’s commit message editor beforehand, so there was no window to catch and remove it before it showed up in git history.<\/p>\n

One developer replaced Copilot’s generated commit message with one they wrote themselves<\/a>, committed, and still found the Copilot co-author line sitting in their log.<\/p>\n

But fret not, as the fix has been delivered<\/a>.<\/p>\n

The Fix\"aDmitriy’s apology over on HackerNews<\/a>.<\/p>\n

Dmitriy, the VS Code team member who merged the original PR, came forward on Hacker News<\/a> over the weekend under the username dmitriv, specifically to address the fallout.<\/p>\n

Identifying himself as the person who approved the change, Dmitriy said that he was sorry for mistakenly turning on this feature by default without sufficient scrutiny.<\/p>\n

Also clarifying the following before the conspiracy theories started emerging:<\/p>\n

There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here – many similar tools do this as well.<\/p>\n

The fix, now live on VS Code’s GitHub repo as PR #313931<\/a>, reverts git.addAICoAuthor back to off by default and corrects the detection issue that caused the trailer to appear even when Copilot was not in use.<\/p>\n

You can expect this change to land with the upcoming VS Code 1.119 release.<\/p>\n

Via: The Register<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"VS Code has been quietly appending a Co-authored-by: Copilot line to users’ git commits, including ones written entirely…\n","protected":false},"author":2,"featured_media":27798,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[420,7853,416,320,7852],"class_list":{"0":"post-27797","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-microsoft","8":"tag-azure","9":"tag-azure-copilot","10":"tag-copilot","11":"tag-microsoft","12":"tag-microsoft-copilot"},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/27797","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=27797"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/27797\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/27798"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=27797"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=27797"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=27797"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}