Change default for git.addAICoAuthor to off#313931
Conversation
Co-authored-by: Copilot <copilot@github.com>
📬 CODENOTIFYThe following users are being notified based on files changed in this PR: @lszomoruMatched files:
|
Screenshot ChangesBase: Changed (28)blocks-ci screenshots changedReplace the contents of Updated blocks-ci-screenshots.md<!-- auto-generated by CI — do not edit manually -->
#### editor/codeEditor/CodeEditor/Dark

#### editor/codeEditor/CodeEditor/Light

#### editor/inlineChatZoneWidget/InlineChatZoneWidget/Dark

#### editor/inlineChatZoneWidget/InlineChatZoneWidget/Light

#### editor/inlineChatZoneWidget/InlineChatZoneWidgetTerminated/Dark

#### editor/inlineChatZoneWidget/InlineChatZoneWidgetTerminated/Light
 |
|
Thanks for listening to the feedback! |
There was a problem hiding this comment.
Pull request overview
This PR changes Git’s AI co-author behavior to be opt-in by default and ensures AI contribution tracking does not run when built-in AI features are disabled.
Changes:
- Set the default for
git.addAICoAuthorto"off"(schema + runtime default). - Prevent AI contribution tracking (
AiContributionFeature) from activating when AI features are disabled/hidden. - Skip adding the AI co-author trailer when
chat.disableAIFeaturesis enabled.
Show a summary per file
| File | Description |
|---|---|
| src/vs/workbench/contrib/editTelemetry/browser/editTelemetryContribution.ts | Gates AiContributionFeature activation behind the entitlement “hidden” state (covers chat.disableAIFeatures). |
| extensions/git/src/repository.ts | Changes default addAICoAuthor fallback to "off" and avoids appending the trailer when AI features are disabled. |
| extensions/git/package.json | Updates the configuration schema default for git.addAICoAuthor to "off". |
Copilot's findings
- Files reviewed: 3/3 changed files
- Comments generated: 0
|
I would not mind it defaulting to on, if it actually works: not only for Copilot, reliable listing the actual model versions used, differentiating between agendic creation and input completion. Being able to reference a session log, helping with logging the evidence needed to get indemification protection. And commit message preview for human. |
Agreed,. model attribution is really needed here, as well as making sure it doesn't catch non-AI changes. |
|
Thank you! Saw your post on hackernews as well. Appreciate the honesty here. |
|
Does this still add the attribution if copilot was active, but not used? Does it still do it silently? |
|
Could we consider completely reverting this default back to |
|
no shot no one at microsoft told you this is a terrible idea XD |
That is exactly what this change is doing - default back to |
With this change, default behavior is there will be no attribution whether Copilot was used or not. So basically by default it works as if this feature does not exist at all. When the setting is on, it will add attribution depending on the setting and there is more work to make sure it works correctly when the setting is 'all' and to make it more visible to the user. |
Big Tech companies are so high on their supply that they'll push obviously awful changes just to please the investors. The worst part isn't that someone didn't think this was a terrible idea, the worst part is that the execs didn't listen to them. |
|
Can we expect more silent and invasive changes in the near future? Were there any similar recent improvements forced by management? I think this was the final straw for most users. Good job, everybody involved. Zed it is. |
|
I genuinely wonder. Why are you all using VSCode at all? Most modern editors have less than maybe 2 days of learning curve. How hot does the water need to be before you decide to jump out? |
You can't just say "most modern editors", and then continue on to not specify a single one lmao. If you want people to move off VSCode, you gotta give them a hint of what to move to. |
Zed. Open-source, Rust, no Electron. |
Their homepage advertises agentic development front and center (literally), I don't see why someone moving away from AI-focused tools would go to a different AI-focused tool. |
It's not AI-focused. In fact you can disable all "AI"-features if you want with a single switch. |
|
The fact this feature flag is still there and after what happened with Recall - absolutely zero trust Microslop won't just sneakily re-enable this at some point. What next? Automatic driving cars co-driven with Jesus taking the wheel? |
|
turn it back on, no balls |
|
|
DID ANYONE THINK FOR ONE SECOND ABOUT THE LEGAL IMPLICATIONS OF THIS???? ARE YOU ALL OUT OF YOUR MINDS. GET YOUR LAWYERS READY. MY CODE IS MY PROPERTY AND FURTHERMORE THAT CHANGE IS PRETTY MUCH ILLEGAL IN THE EU. |
|
Do you folks want to move back to HN for discussion? |
|
This is all so abhorrently stupid, I hope everyone who worked on this pr seriously actually learns something from it |
If there is one thing we should count on, it's MS not learning. |
yeah, keep making fun of people rightfully upset about your reckless decision to forcefully mark their work as "co-authored" by slop, i'm sure that'll get people to trust your product 👍 |
Also making sure change tracking is disabled when AI features are disabled.