<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git Workflow on No Semicolons</title><link>https://nosemicolons.com/tags/git-workflow/</link><description>Recent content in Git Workflow on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Apr 2026 08:43:11 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/git-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Versioning Nightmare: How to Track Changes When Your AI Partner Rewrites Everything</title><link>https://nosemicolons.com/posts/ai-code-versioning-tracking-changes/</link><pubDate>Sat, 25 Apr 2026 08:43:11 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-versioning-tracking-changes/</guid><description>&lt;p>Ever committed code from your AI pair programming session only to realize three months later that you have absolutely no idea what changed or why? Yeah, me too.&lt;/p>
&lt;p>Traditional version control assumes humans are making thoughtful, incremental changes. But when Claude or GPT-4 decides to &amp;ldquo;refactor&amp;rdquo; your 200-line function into a completely different architectural pattern, your git history starts looking like a Jackson Pollock painting—colorful but incomprehensible.&lt;/p>
&lt;p>I&amp;rsquo;ve been wrestling with this problem for the better part of a year, and while I don&amp;rsquo;t have all the answers, I&amp;rsquo;ve found some strategies that actually work. Let me share what I&amp;rsquo;ve learned about taming the AI code versioning nightmare.&lt;/p></description></item></channel></rss>