{"version":"2.1.233","anchor":"worktrees-can-be-created-from-gitlab-merge-requests","canonical_anchor":"worktrees-can-be-created-from-gitlab-merge-requests","heading":"Worktrees can be created from GitLab merge requests","tier":"use","area":"Worktrees","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/worktrees-can-be-created-from-gitlab-merge-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Worktrees can be created from GitLab merge requests\n\nYou can create a worktree from a GitLab merge request number, and the fetch now times out instead of hanging.\n\n**What**\n\nCreating 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.\n\n**Details**\n\n- GitLab remotes fetch `merge-requests\/<n>\/head`, GitHub remotes fetch `pull\/<n>\/head`, and a remote on any other host tries both in turn.\n- The failure message was reworded to cover both kinds of change and to mention timeouts.\n\n**Evidence**\n\n`Failed to fetch PR\/MR #`\n\n- Area: Worktrees\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}