<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Worktrees on deskriders</title>
    <link>/tags/worktrees/</link>
    <description>Recent content in Worktrees on deskriders</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 11 Aug 2026 20:36:06 +0100</lastBuildDate>
    <atom:link href="/tags/worktrees/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Git Worktrees: Multiple Trees, One Repository</title>
      <link>/posts/git-worktrees-tutorial/</link>
      <pubDate>Tue, 11 Aug 2026 20:36:06 +0100</pubDate>
      <guid>/posts/git-worktrees-tutorial/</guid>
      <description>&lt;p&gt;Stop cloning. Stop stashing. Start branching in parallel.&lt;/p&gt;&#xA;&lt;p&gt;Git worktrees give you a second (or third, or tenth) working directory attached to a single repository — the same &lt;code&gt;.git&lt;/code&gt;, the same object database, the same refs — but with an independent working tree, HEAD, and index. One repo, many folders. One &lt;code&gt;.git&lt;/code&gt;, many trees.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-problem--one-working-tree-is-a-bottleneck&#34;&gt;The Problem — One Working Tree Is a Bottleneck&lt;/h2&gt;&#xA;&lt;p&gt;You&amp;rsquo;re 200 lines deep into a feature branch when a critical bug ships to prod. The fix needs &lt;code&gt;main&lt;/code&gt; — but you can&amp;rsquo;t lose your seat. Your IDE indexes are warm, your tests are mid-run, your terminal is full of context.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
