<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Attribution on The Coders Blog</title><link>https://thecodersblog.com/tag/attribution/</link><description>Recent content in Attribution on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 05 May 2026 15:17:36 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/attribution/index.xml" rel="self" type="application/rss+xml"/><item><title>Copilot Co-Authorship: New Standards for AI in Commit Messages</title><link>https://thecodersblog.com/github-commit-message-standards-for-ai-assistance-2026/</link><pubDate>Tue, 05 May 2026 15:17:36 +0000</pubDate><guid>https://thecodersblog.com/github-commit-message-standards-for-ai-assistance-2026/</guid><description>&lt;p&gt;The sudden appearance of &lt;code&gt;Co-authored-by: Copilot &amp;lt;copilot@github.com&amp;gt;&lt;/code&gt; in your Git history, without explicit consent or clear indication of &lt;em&gt;what&lt;/em&gt; was co-authored, is no longer a theoretical problem. It&amp;rsquo;s a stark reminder that the integration of AI into our development workflows demands formalization, transparency, and a clear chain of accountability. The recent shifts in how GitHub Copilot handles commit message attribution highlight a critical juncture: we must move beyond ad-hoc implementations to establish robust standards for AI co-authorship.&lt;/p&gt;</description></item></channel></rss>