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
For large volume repositories (like my main work repo), I've taken to using git worktrees in conjunction with a bare repository to quickly switch contexts without having to worry about stashing/committing, etc. The bare repository is used so that everything is self contained inside a single directory and I don't have worktrees intermingled with the main working tree files.
For a given repository (e.g., devops), the directory structure looks like:
This works great, but until v2.48 git linked worktrees with absolute paths which meant that this devops directory could not be moved without breaking all the worktrees, despite everything being self contained inside the directory. It also meant that the worktrees couldn't be mapped inside containerized environments as the absolute path differed. To solve this, I contributed a patch series that allowed worktrees to be linked with relative paths.
It would be great if jj's workspaces could also be linked with relative paths as they suffer from the same limitations mentioned above.
Thanks!
The text was updated successfully, but these errors were encountered:
Hello!
For large volume repositories (like my main work repo), I've taken to using git worktrees in conjunction with a bare repository to quickly switch contexts without having to worry about stashing/committing, etc. The bare repository is used so that everything is self contained inside a single directory and I don't have worktrees intermingled with the main working tree files.
For a given repository (e.g.,
devops
), the directory structure looks like:This works great, but until v2.48 git linked worktrees with absolute paths which meant that this
devops
directory could not be moved without breaking all the worktrees, despite everything being self contained inside the directory. It also meant that the worktrees couldn't be mapped inside containerized environments as the absolute path differed. To solve this, I contributed a patch series that allowed worktrees to be linked with relative paths.It would be great if jj's workspaces could also be linked with relative paths as they suffer from the same limitations mentioned above.
Thanks!
The text was updated successfully, but these errors were encountered: