dmitriv

5 ms·

1.
by dmitriv 5mo ago
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
2.
by dmitriv 5mo ago
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.
3.
by dmitriv 5mo ago
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.
4.
by dmitriv 5mo ago
I did both, didn't I? :-)
5.
by dmitriv 5mo ago
Correct.
6.
by dmitriv 5mo ago
I really did create a new account to respond :)
7.
by dmitriv 5mo ago
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!
8.
by dmitriv 5mo ago
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 licen
9.
by dmitriv 5mo ago
Agreed, fixed disableAiFeatures in my PR: https://github.com/microsoft/vscode/pull/313931 Will work on making it better later.
10.
by dmitriv 5mo ago
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 impl
11.
by dmitriv 5mo ago
Sorry about that, it's being reverted: https://github.com/microsoft/vscode/pull/313931
12.
by dmitriv 5mo ago
Switched back to opt-in here: https://github.com/microsoft/vscode/pull/313931
13.
by dmitriv 5mo ago
That's ok :-)
14.
by dmitriv 5mo ago
Thanks. Done here: https://github.com/microsoft/vscode/pull/313931
15.
by dmitriv 5mo ago
It would be tricky, yes, since it depends on core editor functionality which is not exposed through the API.
16.
by dmitriv 5mo ago
I don't refuse - what would you like to ask?
17.
by dmitriv 5mo ago
Correct, this was the ask.
18.
by dmitriv 5mo ago
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 :-)
19.
by dmitriv 5mo ago
It is the middle of the night and I am responding. Anything specific you'd like me to respond to?
20.
by dmitriv 5mo ago
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.
21.
by dmitriv 5mo ago
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.
22.
by dmitriv 5mo ago
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.
23.
by dmitriv 5mo ago
Here you go: https://github.com/microsoft/vscode/pull/313931
24.
by dmitriv 5mo ago
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
25.
by dmitriv 5mo ago
Thanks for the PR, I'll work on getting this in.
26.
by dmitriv 5mo ago
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 wa
27.
by dmitriv 5mo ago
Thanks. I guess...
28.
by dmitriv 5mo ago
I didn't. I have locked the comments on a closed PR, and many of those comments were not constructive.
29.
by dmitriv 5mo ago
I'm here, what would you like to know?
30.
by dmitriv 5mo ago
I'm here in case you have something to say to me directly.

More ›