Git worktree integration & awareness.

[trcoffman]

So let's say I have a git repository in ~/src/project. I can use zoxide to easily jump to dirs within the project like ~/src/project/packages/auth and ~/src/project/packages/design-system by just doing z auth and z design.

However, let's say I create another worktree because I want to take a closer look at my coworker's PR but I don't want to disrupt my main directory. Now, I have checked out feature/new-component branch to the directory ~/src/project+new-component.

With the way that zoxide currently works, when I go into that directory and run z design it will take me to ~/src/project/packages/design-system. What I would like would be greater git integration and awareness on the part of zoxide, so that it knew that because I'm in the other worktree that it should take me to ~/src/project+new-component/packages/design-system.

If you run zoxide out of a git directory, it should probably work exactly the same as now. But if you run zoxide within a git directory, it should be more aware of git worktrees. This would be a massive quality of live improvement for worktrees.

[jimmythomson]

This is something that I'd really love to see too. My use case is almost identical.