{"version":"2.1.233","anchor":"gitlab-merge-requests-show-up-in-the-fleet-and-job-views","canonical_anchor":"gitlab-merge-requests-show-up-in-the-fleet-and-job-views","heading":"GitLab merge requests show up in the fleet and job views","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/gitlab-merge-requests-show-up-in-the-fleet-and-job-views","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### GitLab merge requests show up in the fleet and job views\n\nFleet and job views now recognise GitLab merge request links and label them \"mr\".\n\n**What**\n\nRows linking to a GitLab merge request are now recognised and labelled \"mr\" instead of \"pr\", and merge request numbers are parsed out of URLs and free text. Previously only GitHub `\/pull\/` links were matched anywhere in these views.\n\n**Details**\n\n- The per-number matcher accepts either `pull` or `-\/merge_requests`, and the free-text parser falls back to `\/\\\/-\\\/merge_requests\\\/(\\d+)(?!\\d)\/`.\n- The badge is passed a kind computed from the link target: \"mr\" when the href matches a merge-request path, \"pr\" otherwise.\n- The URL-to-number parser gained a matching merge-request branch.\n\n**Evidence**\n\n`\/\\\/-\\\/merge_requests\\\/\\d\/`, `return \/\\\/-\\\/merge_requests\\\/\\d\/.test(e.href) ? \"mr\" : \"pr\";`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}