<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Version Control on The Coders Blog</title><link>https://thecodersblog.com/tag/version-control/</link><description>Recent content in Version Control 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/version-control/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><item><title>Beyond GitHub: Why Developers Still Dream of Owning Their Code Forge in 2026</title><link>https://thecodersblog.com/if-i-could-make-my-own-github-2026/</link><pubDate>Fri, 01 May 2026 11:31:06 +0000</pubDate><guid>https://thecodersblog.com/if-i-could-make-my-own-github-2026/</guid><description>&lt;p&gt;For years, GitHub has been our comfortable digital home, but a growing unease whispers in the background: are we renting, or are we truly owning our most critical infrastructure?&lt;/p&gt;
&lt;p&gt;This isn&amp;rsquo;t about shunning collaboration; it&amp;rsquo;s about re-evaluating where our core development assets reside. The conversation about a &amp;ldquo;new forge&amp;rdquo; or a &amp;ldquo;self-hosted GitHub&amp;rdquo; isn&amp;rsquo;t merely academic in 2026; it&amp;rsquo;s a strategic imperative for many.&lt;/p&gt;
&lt;h2 id="the-shifting-sands-of-centralized-code-forges-and-why-were-uneasy"&gt;The Shifting Sands of Centralized Code Forges (and why we&amp;rsquo;re uneasy)&lt;/h2&gt;
&lt;p&gt;The undeniable convenience and network effect of platforms like &lt;strong&gt;GitHub&lt;/strong&gt;, &lt;strong&gt;GitLab.com&lt;/strong&gt;, and &lt;strong&gt;Bitbucket Cloud&lt;/strong&gt; are powerful. They offer instant access, shared tooling, and a vast ecosystem of integrations, making them the default choice for millions of developers and organizations. Yet, this very convenience masks a growing fragility.&lt;/p&gt;</description></item><item><title>Rocky: Rust SQL Engine with Data Versioning 2026</title><link>https://thecodersblog.com/rocky-a-rust-sql-engine-with-advanced-data-versioning-2026/</link><pubDate>Wed, 29 Apr 2026 10:02:14 +0000</pubDate><guid>https://thecodersblog.com/rocky-a-rust-sql-engine-with-advanced-data-versioning-2026/</guid><description>&lt;p&gt;The landscape of data management is perpetually evolving, demanding more robust, auditable, and flexible systems. Today, we introduce Rocky, a novel SQL engine engineered in Rust, fundamentally reshaping how developers interact with data through advanced versioning capabilities. Rocky integrates Git-like data branching, comprehensive replay functionality, and granular column lineage, addressing critical challenges in data integrity, collaboration, and debugging for modern data-intensive applications.&lt;/p&gt;
&lt;h3 id="data-branching-git-native-version-control-for-your-database"&gt;Data Branching: Git-Native Version Control for Your Database&lt;/h3&gt;
&lt;p&gt;Rocky&amp;rsquo;s core innovation lies in its native support for data branching. This mechanism mirrors the workflow familiar to every software developer using Git, allowing for the creation of isolated, mutable copies of a database&amp;rsquo;s state. Instead of managing schema changes or data transformations through cumbersome migrations or staging environments, developers can now &lt;code&gt;BRANCH&lt;/code&gt; their entire database.&lt;/p&gt;</description></item></channel></rss>