{"version":"2.1.233","anchor":"gitlab-merge-request-urls-are-recognised-like-github-pull-re","canonical_anchor":"gitlab-merge-request-urls-are-recognised-like-github-pull-re","heading":"GitLab merge request URLs are recognised like GitHub pull requests","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/gitlab-merge-request-urls-are-recognised-like-github-pull-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### GitLab merge request URLs are recognised like GitHub pull requests\n\nPasting a GitLab merge request URL now resolves to a number just like a GitHub pull request.\n\n**What**\n\nPasting a GitLab merge request URL now resolves to a number the same way a GitHub pull request URL does, and the row is labelled per provider.\n\n**Details**\n\n- A second URL pattern matches `\/-\/merge_requests\/<n>`, with optional trailing slash, query or fragment.\n- The row renderer computes a kind from the link, returning \"mr\" for merge request links and \"pr\" for everything else.\n\n**Evidence**\n\n`\/^https?:\\\/\\\/[^\/]+\\\/[^?#]+\\\/-\\\/merge_requests\\\/(\\d+)\\\/?(?:[?#].*)?$\/i`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}