<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/git-workflow/</link><description>Recent content in Git Workflow on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/git-workflow/index.xml" rel="self" type="application/rss+xml"/><item><title>The Power of Virtual Branches: Isolating Your Development Work</title><link>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/power-of-virtual-branches/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/gitbutler-workflow-guide-2026/power-of-virtual-branches/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future Git master! In the previous chapter, we got GitButler up and running and connected our first repository. Now, it&amp;rsquo;s time to dive into the very heart of what makes GitButler so revolutionary: &lt;strong&gt;virtual branches&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Think about your current Git workflow. How often do you find yourself needing to switch contexts, stash changes, or deal with a cluttered local repository because you&amp;rsquo;re working on multiple things at once? Traditional Git branches are powerful, but they can sometimes feel clunky for managing rapid, iterative local development. GitButler&amp;rsquo;s virtual branches are designed to solve exactly these pain points, offering an unparalleled way to isolate your work, experiment freely, and keep your local repository pristine.&lt;/p&gt;</description></item></channel></rss>