You can create a worktree from a GitLab merge request number, and the fetch now times out instead of hanging.
What's wrong with this entry?
Creating a worktree from a change number now works on GitLab as well as GitHub. The ref fetched depends on the remote host, and the fetch now times out rather than hanging.
- GitLab remotes fetch
merge-requests/<n>/head, GitHub remotes fetchpull/<n>/head, and a remote on any other host tries both in turn. - The failure message was reworded to cover both kinds of change and to mention timeouts.
Failed to fetch PR/MR #
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
worktree.locationsetting for Desktop SSH sessionsBoth mention worktree
-
v2.1.246
Worktree cleanup only removes directories Claude Code created
Both mention worktree
-
v2.1.247
Cloud-session seeding names linked worktrees and split git layouts as un-seedable
Both mention worktree