Visual Studio Code (VS Code) is changing how it attributes commits made with the assistance of GitHub Copilot. A recent pull request (PR #310226) details a change to automatically include 'Co-Authored-by Copilot' in the author metadata of every commit.
What Happened
According to the GitHub pull request, the change aims to improve attribution for code generated with Copilot. The PR merges a commit that modifies VS Code to unconditionally add the 'Co-Authored-by Copilot' trailer to the git author metadata. This means every commit, even those written entirely by the developer without any Copilot suggestions accepted, will include this attribution. The PR description does not detail a user setting to disable this behavior.
Why It Matters
This change has significant implications for developers and version control hygiene. While acknowledging Copilot's assistance can be valuable, automatically attributing it to every commit, even when unused, introduces noise into the commit history. This makes it more difficult to discern which commits genuinely benefited from Copilot's suggestions.
More importantly, the automatic attribution could raise concerns about accurate code ownership and licensing. While the intent is to provide attribution, the blanket application could dilute the significance of the attribution when Copilot did contribute substantially.
Currently, the change appears to be enabled by default and there is no documented way to disable it. This lack of user control is a key concern raised by developers reacting to the change. There is potential for impacts on automated tooling that parses commit messages and identifies authors. The change may require updates to tools that rely on accurate author information.
What To Watch
The developer community is actively discussing the implications of this change on the PR itself and other platforms. It remains to be seen if Microsoft will respond to these concerns and provide a configuration option to disable the automatic attribution. Further, it's unclear how this change will interact with existing CI/CD pipelines and other tooling that relies on commit metadata. Developers should monitor the GitHub PR for updates and potential revisions to this behavior.