<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Branching on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/branching/</link><description>Recent content in Branching 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/branching/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 5: Branching for Freedom: Developing Features Safely</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-5-branching-for-freedom/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-5-branching-for-freedom/</guid><description>&lt;h2 id="introduction-branching-for-freedom"&gt;Introduction: Branching for Freedom!&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 5, where we unlock one of Git&amp;rsquo;s most powerful features: &lt;strong&gt;branching&lt;/strong&gt;! Up until now, we&amp;rsquo;ve been working on a single timeline, making commits one after another. This is great for solo projects, but what happens when you want to develop a new feature without breaking the existing, stable version of your code? Or when multiple team members need to work on different parts of a project simultaneously?&lt;/p&gt;</description></item><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><item><title>Chapter 7: Undoing Mistakes: Revert, Reset, and Amend</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-7-undoing-mistakes/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-7-undoing-mistakes/</guid><description>&lt;h2 id="chapter-7-undoing-mistakes-revert-reset-and-amend"&gt;Chapter 7: Undoing Mistakes: Revert, Reset, and Amend&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid developer! In our journey through Git, we&amp;rsquo;ve learned how to create snapshots of our work (commits), organize them into branches, and even merge them together. But what happens when you make a mistake? A wrong file committed, a typo in a commit message, or a feature that needs to be completely removed?&lt;/p&gt;
&lt;p&gt;Fear not! Git is incredibly forgiving, offering several powerful tools to &amp;ldquo;undo&amp;rdquo; changes. This chapter is your guide to mastering these essential recovery techniques. We&amp;rsquo;ll explore &lt;code&gt;git revert&lt;/code&gt;, &lt;code&gt;git reset&lt;/code&gt;, and &lt;code&gt;git commit --amend&lt;/code&gt;, understanding their distinct purposes, how they affect your project&amp;rsquo;s history, and when to use each safely and effectively. By the end, you&amp;rsquo;ll be able to confidently correct errors without breaking your project or confusing your teammates.&lt;/p&gt;</description></item><item><title>Chapter 9: Advanced Branching Strategies and Workflows</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-9-advanced-branching-strategies/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-9-advanced-branching-strategies/</guid><description>&lt;h2 id="introduction-to-advanced-branching-strategies"&gt;Introduction to Advanced Branching Strategies&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid version control explorer! In our previous chapters, you mastered the fundamentals of Git, learning how to create branches, switch between them, and merge your changes back into the main line of development. You understand the power of isolated development, but what happens when an entire team, or even multiple teams, need to collaborate on a large, complex project? How do you keep everyone&amp;rsquo;s work organized, prevent chaos, and ensure a stable, deployable product?&lt;/p&gt;</description></item><item><title>Chapter 15: Troubleshooting Common Git &amp;amp; GitHub Problems</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-15-troubleshooting-common-problems/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-15-troubleshooting-common-problems/</guid><description>&lt;h2 id="introduction-when-things-go-sideways"&gt;Introduction: When Things Go Sideways&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15! So far, we&amp;rsquo;ve explored the incredible power of Git and GitHub for managing code, collaborating with teams, and building amazing projects. But let&amp;rsquo;s be honest: even the most experienced developers sometimes face a hiccup or two. Git, while powerful, can sometimes feel a bit like a puzzle when things don&amp;rsquo;t go exactly as planned.&lt;/p&gt;
&lt;p&gt;This chapter is your trusty toolkit for those &amp;ldquo;uh-oh&amp;rdquo; moments. We&amp;rsquo;re going to dive deep into diagnosing and fixing the most common Git and GitHub issues you&amp;rsquo;ll encounter in real-world development. From dreaded merge conflicts to accidental changes and mysterious &amp;ldquo;detached HEAD&amp;rdquo; states, we&amp;rsquo;ll cover it all. Our goal isn&amp;rsquo;t just to give you solutions, but to help you understand &lt;em&gt;why&lt;/em&gt; these problems occur and how to confidently navigate them yourself.&lt;/p&gt;</description></item></channel></rss>