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
{{ message }}
This repository was archived by the owner on Sep 11, 2020. It is now read-only.
When attempting to clone a repository containing symlinks, the links are created as regular files directly from the object blobs - i.e, the file contents is the symlink target.
I started an attempt to implement the correct behaviour in Worktree.checkoutEntry() but it looks like the filesystem abstraction does not support symlink creation.
The following snippet clones a repo that demonstrates the issue.
👍 I'm happy to contribute towards this with some guidance. I expect the os based implementation will be straight forward, but I wasn't sure how to tackle the memory implementation.
When attempting to clone a repository containing symlinks, the links are created as regular files directly from the object blobs - i.e, the file contents is the symlink target.
I started an attempt to implement the correct behaviour in
Worktree.checkoutEntry()
but it looks like the filesystem abstraction does not support symlink creation.The following snippet clones a repo that demonstrates the issue.
The text was updated successfully, but these errors were encountered: