{"version":"2.1.323","anchor":"gitlab-merge-request-badge","canonical_anchor":"gitlab-merge-request-badge","heading":"A GitLab merge request badge that uses the glab tool","tier":"notice","area":"GitLab","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/gitlab-merge-request-badge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A GitLab merge request badge that uses the glab tool\n\nA new badge for GitLab merge requests runs the glab command-line tool in your session's folder, with safety checks first\n\n**Unclear.** The default of the switch that controls the badge is not known, so it is unclear whether the badge appears.\n\n**What**\n\nClaude Code has a new badge for GitLab merge requests. A merge request is GitLab's name for a proposed code change. To fill the badge, Claude Code looks for the `glab` command-line tool and runs it in the session's folder. It does not run `glab` when:\n\n- a local `glab` configuration is found\n\n- the folder is an outside checkout\n\n- it cannot work out which folder to run `glab` in\n\nThe badge sits behind a remote switch.\n\n**Why**\n\nIf you use GitLab, you may see a badge for your merge request.\n\n- Area: GitLab\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}