On Mon, Nov 18, 2019 at 1:51 AM Johannes Sixt <j6t@xxxxxxxx> wrote: > Am 18.11.19 um 05:32 schrieb Sivanandan Srilakshmanan: > > I was reluctant to create clones of each project on my local machine > > each with it's own "main working tree" > > > > I figured:- > > > > I could setup a "Local bare repository" and create remote link to the > > hosted git repositories. > > (https://git-scm.com/docs/git-worktree#_list_output_format) > > > > Create "Local branches" when needed. Create a "linked working tree" > > associated with the local branch. > > > > This way I can have a single repository pointing to multiple remote > > repositories on one side and managing multiple local directories on my > > PC. > > In summary, my local repository will be conduit. I guess this is not possible. > > I think it is possible. Just don't make it a bare repository if you need > to create secondary worktrees. (But maybe it even works if it is bare; > just don't set GIT_DIR; I don't do it this way, so I cannot tell.) git-worktree explicitly supports the use-case of the main worktree being bare. (Of course, in this case, it's a misnomer to call it the "main _worktree_", but the terminology was already established by the time explicit support for bareness was added, so the term "main worktree" stuck.)
