[FEATURE REQUEST]: git worktree support

[ferdinandyb]

This may not be in scope for the project, in that case, please close and disregard. I'm also not quite sure how to best solve this, but here is the problem I keep having:

While working on separate PR-s I tend use git worktree a lot. I also find myself wanting to go to a couple of rather nested directories. Unfortunately, zoxide in this case would always take me into the original repository, since that's where I touch those paths the most often. It would be really awesome to be able to use zoxide to navigate inside a specific worktree, but to the often used paths.

One way I could imagine this is a new flag, which when invoked does something like the following:

• it checks if it is evoked within a git repository
• if it's a repository it lists all worktrees
• if the selected path is a subpath of any worktree, it is assumed the user wants to navigate inside the worktree, so based on the list of worktree paths, the worktree is stripped from the selection and the current worktree is added

Just mentioning, that I saw a similar issue, which did not receive comments and was ultimately closed by the author:
#528

I think this is something I could implement as a wrapper myself, but thought could be something zoxide suppports out of the box.

[ferdinandyb]

Workaround shell script

[gauravjuvekar]

Dupe of #863 ?

[ferdinandyb]

Idea: add a shell function zz : search subdirs: --basedir=(pwd)

I will need to check this, but my hunch is that this will not help too much, in a new worktree, since the user will never have traversed any paths in a newly created worktree. From my understanding the above flags just scopes the query to any folders we have already touched under the one specified.

What I would be interested in is zoxide learning the layout of the project and applying that straight away in a new worktree.