VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

Post by PunchyHamster » Sun, May 03, 2026, 9:27 AM UTC

parineum wrote: post #391

krupan wrote: post #387

Earlier quoted context omitted.

This comment and a few others here make me feel old and sad for the people too young to remember that time. Yes, Google was an enormous breath of fresh air when it came out. 1000% better UI and features than the competition. Search was incredible. Gmail was a revelation. The whole company culture was night and day compared to the stodgy old tech companies like IBM. Just mind blowingly awesome. And then maps?? How did…

They basically revolutionized the web with the JavaScript V8 engine in chrome. Before them, JavaScript performance was so bad you had to have a really light touch with it.

Post by dmitriv » Sun, May 03, 2026, 9:28 AM UTC

gizzlon wrote: post #573

galonk wrote: post #546

Earlier quoted context omitted.

They pretended to be fronting up but didn’t respond to anything after that. Doesn’t seem very commendable to me.

their comments are dead, probably related to it being a new account

Post by PunchyHamster » Sun, May 03, 2026, 9:30 AM UTC

somebehemoth wrote: post #349

dmitriv wrote: post #268

I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. 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. Obviously, it should not be on…

I think the constructive criticism is best directed at whatever process you are following. That process allowed a very visible user facing change in a widely used piece of software. How did this change make it to production without some process catching the impact of this change? Was there really no internal discussion from a code review at least? This seems hard for me to believe. I expect more from Microsoft.

Post by PunchyHamster » Sun, May 03, 2026, 9:31 AM UTC

jdenning wrote: post #608

dmitriv wrote: post #268

I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation. 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. Obviously, it should not be on…

What is the use-case where you expect users would be happy that you modify their commit messages with MS marketing? Do you think it would be ok to edit every commit to append “written with VS Code”?

Post by dmitriv » Sun, May 03, 2026, 9:37 AM UTC

rmunn wrote: post #386

bsuvc wrote: post #312

Earlier quoted context omitted.

Why did you lock the comments on the GitHub issue? (Edit: I meant to say PR, not issue...)

I'm not him, but it was pretty obvious that the comments section was going to be attracting more and more people saying the same thing that had already been said before, and that no useful discussion was going to be had. At some point the value of spamming everyone who commented on the issue with a notification (which puts an email in your inbox if you haven't changed the default setting) becomes lower and lower. I'v…