<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git Workflows on No Semicolons</title><link>https://nosemicolons.com/tags/git-workflows/</link><description>Recent content in Git Workflows on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Jul 2026 10:09:26 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/git-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Merge Hell: How to Resolve Conflicts When 4 Developers Use Different Models on the Same Feature</title><link>https://nosemicolons.com/posts/ai-code-generation-merge-conflicts-multiple-models/</link><pubDate>Wed, 08 Jul 2026 10:09:26 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-merge-conflicts-multiple-models/</guid><description>&lt;p>Picture this: Sarah uses GPT-4 to scaffold her React components, Jake swears by Claude for refactoring logic, Maria leans on Gemini for data processing, and Alex lets Copilot autocomplete everything. They&amp;rsquo;re all brilliant developers working on the same feature branch, but when merge time comes&amp;hellip; it&amp;rsquo;s absolute chaos.&lt;/p>
&lt;p>Sound familiar? Welcome to the brave new world of multi-model development teams, where AI code merge conflicts aren&amp;rsquo;t just about different coding styles—they&amp;rsquo;re about fundamentally different AI approaches to solving the same problems.&lt;/p></description></item></channel></rss>