Hello, I recently learned about worktrees in git and I was wondering if some extra tooling could benefit workflows that lean on it? These are the use cases I have banging around in my head: - throwaway/temp workspaces One use case that I've seen alot is creating a workspace to handle some hotfix and/or debugging and possibly commit the fix. Instead of needing to actively manage this workspace (mostly the cleanup) I imagine it would not be too dificult to these in the /tmp folder and then cleanup/ignore their entries. Temp workspace file paths might make this kind of tooling pointless unless you also automatically change the working directory to the new workspace.. I've seen people advocate for a git aliases that jump between workspaces but if your adding the workspace and typing out the file path anyways then `cd path` is shorter than an alias anyways. - move hunks between workspaces In my experience it's more common for a hotfix/debugging use case to get the report and just use the current branch since it's not often that your current branch is either completely broken or directly conflicts with the reported bug. I usually don't stashing and changing branches until I've got a fix and want to commit it. I recently tried a workspace for this situation but I ended needing to retype the fix in the new workspace, after reflecting a bit I should be able to do `git stash -p` in the main workspace then `git stash pop` in the new worktree but a dedicated way to move hunks would be quite useful. I think there could be more opportunities for general use cases to benefit from workspaces if there were extra workspace tooling but these are the only ones I can think of, also to be clear I'm not really considering any tooling that would allow workspaces to do something you can't already do with git in some other way. Thoughts? Regards, Thomas
