Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.233 Home All releases ←olderv2.1.232 v2.1.234newer→
Claude Code v2.1.233

GitLab merge requests show up in the fleet and job views

You'll notice
Useful2 Signal1
Git Integration

Fleet and job views now recognise GitLab merge request links and label them "mr".

What

Rows 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.

Details
  • The per-number matcher accepts either pull or -/merge_requests, and the free-text parser falls back to /\/-\/merge_requests\/(\d+)(?!\d)/.
  • The badge is passed a kind computed from the link target: "mr" when the href matches a merge-request path, "pr" otherwise.
  • The URL-to-number parser gained a matching merge-request branch.
Evidence

/\/-\/merge_requests\/\d/, return /\/-\/merge_requests\/\d/.test(e.href) ? "mr" : "pr";

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.

See this entry in the whole of v2.1.233 →