<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Collaboration on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/code-collaboration/</link><description>Recent content in Code Collaboration on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/code-collaboration/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 6: Resolving Merge Conflicts: When Changes Collide</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-6-resolving-merge-conflicts/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-6-resolving-merge-conflicts/</guid><description>&lt;h2 id="chapter-6-resolving-merge-conflicts-when-changes-collide"&gt;Chapter 6: Resolving Merge Conflicts: When Changes Collide&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our previous chapters, we learned the magic of branching – how to create separate lines of development to work on features or fixes without disturbing the main codebase. We even touched upon merging, bringing those separate lines back together. But what happens when two brilliant minds (or even one mind working on two branches!) make conflicting changes to the &lt;em&gt;exact same part&lt;/em&gt; of the &lt;em&gt;same file&lt;/em&gt;?&lt;/p&gt;</description></item></channel></rss>