You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 1.110, we added a setting to add Copilot as coauthor in commit messages by appending Co-authored-by: Copilot copilot@github.com. The setting git.addAICoAuthor has three different values:
off - no attribution no matter whether Copilot assisted or not with the code in this commit
chatAndAgent - add attribution if the commit contains code that was generated using the chat feature
all - add attribution if the commit contains any kind of AI-generated code (chat, inline completions, NES)
The default value of the setting was off.
In 1.117 (public rollout started 4/22), we changed the setting default to all. There was a bug in the code that was not found in testing that attributed non-Copilot code completions to Copilot. This resulted in commit messages containing Co-authored-by: Copilot copilot@github.com even when the disableAIfeatures setting was turned on. This issue is tracked in #313064.
Because of the bug, we changed the setting value to chatAndAgent in 1.118 (public rollout started 4/29).
You can disable the functionality by explicitly turning the feature off in user settings: "git.addAICoAuthor": "off".
What is happening now?
We reverted the default for the AI attribution feature back to off. We also ensure that the feature is disabled when disableAIFeatures is set to true no matter the value of git.addAICoAuthor. This was done in Change default for git.addAICoAuthor to off #313931. These fixes will be tested and released in 1.119 (public rollout starting 5/6).
We are reviewing our test and release processes for gaps to ensure we prevent similar issues in the future.
What will happen to the feature?
Thank you for all your feedback. We'll make/retain the following changes:
The attribution is never applied for changes that are not AI-related.
Before adding a commit trailer, the user will have to give consent, no matter the default value of the setting.
We will work on these improvements and iterate with the community via issues and discussions on GitHub to make sure the bugs are fixed and concerns are addressed.
What happened?
In 1.110, we added a setting to add Copilot as coauthor in commit messages by appending
Co-authored-by: Copilot copilot@github.com. The settinggit.addAICoAuthorhas three different values:off- no attribution no matter whether Copilot assisted or not with the code in this commitchatAndAgent- add attribution if the commit contains code that was generated using the chat featureall- add attribution if the commit contains any kind of AI-generated code (chat, inline completions, NES)The default value of the setting was
off.In 1.117 (public rollout started 4/22), we changed the setting default to
all. There was a bug in the code that was not found in testing that attributed non-Copilot code completions to Copilot. This resulted in commit messages containingCo-authored-by: Copilot copilot@github.comeven when thedisableAIfeaturessetting was turned on. This issue is tracked in #313064.Because of the bug, we changed the setting value to
chatAndAgentin 1.118 (public rollout started 4/29).You can disable the functionality by explicitly turning the feature off in user settings:
"git.addAICoAuthor": "off".What is happening now?
off. We also ensure that the feature is disabled whendisableAIFeaturesis set to true no matter the value ofgit.addAICoAuthor. This was done in Change default for git.addAICoAuthor to off #313931. These fixes will be tested and released in 1.119 (public rollout starting 5/6).What will happen to the feature?
Thank you for all your feedback. We'll make/retain the following changes:
Assisted-byinstead ofCo-authored-byfor AI agents #313962.We will work on these improvements and iterate with the community via issues and discussions on GitHub to make sure the bugs are fixed and concerns are addressed.