title: What would I use git-worktree for?
body: <p>I read <a href="https://github.com/blog/2042-git-2-5-including-multiple-worktrees-and-triangular-workflows">Github's post on git-worktree</a>. They write:</p>
  
  <blockquote>
    <p>Suppose you're working in a Git repository on a branch called <code>feature</code>, when a user reports a high-urgency bug in <code>master</code>. First you create a linked working tree with a new branch, <code>hotfix</code>, checked out relative to master […] You can fix the bug, push hotfix, and create a pull request.</p>
  </blockquote>
  
  <p>When I'm working on a branch called feature and some high-urgency bug in master is reported, I usually stash away whatever I'm working on and create a new branch. When I'm done, I can continue working. This is a very simple model, I've been working like that for years.</p>
  
  <p>On the other hand, using git-worktree has its own limitations:</p>
  
  <blockquote>
    <p>For example, it's not allowed to have the same branch checked out in two linked working trees at the same time, because that would allow changes committed in one working tree to bring the other one out of sync.</p>
  </blockquote>
  
  <p>Why would I choose a more complicated workflow for a problem that's already been solved?</p>
  
  <p><strong>Is there anything about <code>git-worktree</code> that couldn't be done beforehand and that justifies this whole new, complex feature?</strong></p>