I work in a Flutter repo that pins its engine via a symlink to a version installed on the local machine. It'd be great to have apply carry this symlink into new worktrees as currently they're explicitly skipped.
A sensible default for links resolving inside the repo would probably be to re-point at the corresponding path in the new worktree. Links pointing outside the repo (like my case) would copy over as-is.
I'd love to hear thoughts, very happy to open a PR for this. Appreciate your work on this excellent tool!
I work in a Flutter repo that pins its engine via a symlink to a version installed on the local machine. It'd be great to have
applycarry this symlink into new worktrees as currently they're explicitly skipped.A sensible default for links resolving inside the repo would probably be to re-point at the corresponding path in the new worktree. Links pointing outside the repo (like my case) would copy over as-is.
I'd love to hear thoughts, very happy to open a PR for this. Appreciate your work on this excellent tool!