title: Is there a good reason why working trees should be created at the same directory hierarchy level as the git repo?
body: <p>When I went through many tutorials related to <code>git worktree</code>, everywhere in the command which was used to demonstrate the creation of worktree, <code>..</code> was used for the path where the working tree should be created - which indicates that the new working tree directory to be created at the same directory hierarchy level as that of the git repo.</p>
  <p>An example taken from the <a href="https://git-scm.com/docs/git-worktree#_examples" rel="nofollow noreferrer">git website</a></p>
  <pre><code>git worktree add -b emergency-fix ../temp master
  </code></pre>
  <p>And another from <a href="https://spin.atomicobject.com/2016/06/26/parallelize-development-git-worktrees/" rel="nofollow noreferrer">Atomic Object</a>-</p>
  <pre><code>git worktree add ../new-worktree-dir some-existing-branch
  </code></pre>
  <p>So I am wondering is there a good reason to create worktree at the same directory hierarchy as the git repo?</p>
  <p>Technically, you can create the working tree inside the git repo also. Git allows it.</p>
  <p>And I feel creating all the worktree belonging to a particular <code>git repo</code> under the git repo directory would give a logical grouping.</p>
  <pre><code>git worktree add -b emergency-fix ./temp master
  </code></pre>