Would it be possible to add a config option to allow a custom path naming convention for the worktree folder. For example, currently let's say i have a folder named my-app. When i create a worktree it creates this as my-app-feature. What I want it to do is create it here instead my-app-worktrees/feature. It looks like this is how it works with the global config option for worktreepath but i want it in the same location just not in a folder like that.
The reason around this is if you have multiple repositories (let's say 10) in that same directory you and you create 5 features for each of those repositories you now end up with 60 folders in that directory. If you were able to specify to put them under the new path you would only end up with 20 folders and each of the features would be under that folder.
Let me know if you have any questions. If you are not wanting to provide this functionality to the tool, would you be willing to accept a PR for it?
Would it be possible to add a config option to allow a custom path naming convention for the worktree folder. For example, currently let's say i have a folder named
my-app. When i create a worktree it creates this asmy-app-feature. What I want it to do is create it here insteadmy-app-worktrees/feature. It looks like this is how it works with the global config option for worktreepath but i want it in the same location just not in a folder like that.The reason around this is if you have multiple repositories (let's say 10) in that same directory you and you create 5 features for each of those repositories you now end up with 60 folders in that directory. If you were able to specify to put them under the new path you would only end up with 20 folders and each of the features would be under that folder.
Let me know if you have any questions. If you are not wanting to provide this functionality to the tool, would you be willing to accept a PR for it?