dmitriv

FYI - we have posted update on the subject with more details, links and analysis here: https://github.com/microsoft/vscode/issues/314311

Hopefully this answers some more of the questions raised here. It also incorporates a lot of feedback from this thread with respect to next steps (thank you!).

The fact that non-AI changes are attributed to Copilot is a bug. The intent was to allow customers to add attribution of AI-generated code. As with any bug, it was not intetional.

Thank you so much for explaining the exact reason I did it!

I am reading all pings from GitHub on VS Code and this was just turning into a stream of spam that wasn't adding much new information.

I did both, didn't I? :-)

Correct.

I really did create a new account to respond :)

I think this is a good point - perhaps there should be some commit-time UI which would let the user make the choice. Thanks for the suggestion!

First comment does not sound constructive - are you interested in my opinion on (n)vim?

I am not a legal, so can't comment on legal things. However, I have already responded elsewhere here that this feature has nothing to do with licensing or ownership and was added for those that want the attribution. I understand the desire to see anything Microsoft as bad and evil, but we are really just trying to make a better experience.

I'll respond to the third one, thanks!

Agreed, fixed disableAiFeatures in my PR: https://github.com/microsoft/vscode/pull/313931 Will work on making it better later.

The change was about helping teams ensure AI-generated code is attributed in commits - nothing to do with copyrights and the like. If you don't have to take my word for it - query VS Code repo for changes and issues that went into implementing this and you will see.

Sorry about that, it's being reverted: https://github.com/microsoft/vscode/pull/313931

Switched back to opt-in here: https://github.com/microsoft/vscode/pull/313931

That's ok :-)

Thanks. Done here: https://github.com/microsoft/vscode/pull/313931

It would be tricky, yes, since it depends on core editor functionality which is not exposed through the API.

I don't refuse - what would you like to ask?

Correct, this was the ask.

Good feedback, there needs to be a more explicit opt-in into this for teams that want it. FWIW nobody's performance here will improve from having this metric :-)

It is the middle of the night and I am responding. Anything specific you'd like me to respond to?

Agreed on both points. Having it shown before going into the commit would let the developer decide whether they want it. #2 is fixed in my PR.

I am reverting it because there are bug in the feature and it obviously does not work as expected. Any feedback is important, HN or not.

Fair point. We did catch it internally in testing (as we use VS Code for all our work, so some folks did stumble on it), but I think we underestimated the impact and should do a better job at that.

There are customers who would like to see attribution on changes where AI contributed (companies, users, etc). True, that's not everyone, but you can query our repo for the issues for which this feature was implemented.

The rationale I suppose is those customers what to be more careful with code that was contributed by AI.

HTH

If what you described would make it to our PR queue, it would definitely not pass the gates.

The idea was to track AI-only changes and add the trailer when such changes were detected AND the setting was enabled. Obviously, we didn't want to attribute all changes to AI. There is a bug in change detection (which slipped through testing), which led to even non-AI changes being tracked. And thus we have this problem.

The PR linked here wasn't even implementing the feature, it was changing the default for the setting.