<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/git/</link><description>Recent content in Git 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/categories/git/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></channel></rss>