You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the .git file inside the worktrees references the main worktree via an absolute path. Same for the worktree symlinks in .git-main-working-tree/worktrees/{worktree}/commondir.
This means that whenever you move the whole worktree, the whole thing breaks.
Using git worktree actually leads to the same behaviour, so grm at least does not behave worse than git here.
I'm not sure whether using relative paths is something that git supports and libgit2 exposes. But would be really cool to have if possible. I'd rather not hack this manually, so if it's not exposed by libgit2, the behaviour just has to be accepted.
To do
Check whether there is any way to make git use relative paths
Check whether the functionality is there in libgit2
Implement it in grm if possible. Relative paths should be the default. This would break moving single worktrees, but that is something that would not be supported anyway.
Make it explicit in the docs that moving worktrees is not supported. If really necessary, there could be a separate command to do this. But I'm 99% certain that this is not required.
The text was updated successfully, but these errors were encountered:
Currently, the
.git
file inside the worktrees references the main worktree via an absolute path. Same for the worktree symlinks in.git-main-working-tree/worktrees/{worktree}/commondir
.This means that whenever you move the whole worktree, the whole thing breaks.
Using
git worktree
actually leads to the same behaviour, sogrm
at least does not behave worse than git here.I'm not sure whether using relative paths is something that git supports and libgit2 exposes. But would be really cool to have if possible. I'd rather not hack this manually, so if it's not exposed by libgit2, the behaviour just has to be accepted.
To do
git
use relative pathsgrm
if possible. Relative paths should be the default. This would break moving single worktrees, but that is something that would not be supported anyway.The text was updated successfully, but these errors were encountered: