Currently, users may encounter "filename too long" errors when creating worktrees in repositories with deep directory structures.
Investigate enabling long path support for Git operations performed by the extension (e.g. process-scoped core.longpaths=true) to avoid requiring users to modify their global Git configuration.
Related user report:
"I tried to use it for creating worktrees but got an error saying the filename is too long. I used to have repositories with longer filenames.
I'd to manually run the git command to get this sorted.
git config "--global" core.longpaths true"
Currently, users may encounter "filename too long" errors when creating worktrees in repositories with deep directory structures.
Investigate enabling long path support for Git operations performed by the extension (e.g. process-scoped
core.longpaths=true) to avoid requiring users to modify their global Git configuration.Related user report:
"I tried to use it for creating worktrees but got an error saying the filename is too long. I used to have repositories with longer filenames.
I'd to manually run the git command to get this sorted.
git config "--global" core.longpaths true"