glab(1)

📦
version 1.128.0 · 5 versions
, in arch rolling

NAME 💖 (welcome to the glab(1) manual, bestie)

glab-mr-note-resolve — Resolve a discussion on a merge request. (EXPERIMENTAL)

📜 SYNOPSIS 📜

Exact source synopsis, no edits, because we respect the source:

glab mr note resolve [ | ]  [flags]

✨ DESCRIPTION ✨

Okay so this command resolves a discussion on a merge request. That’s the whole vibe. 💅

The identifier can be one of the following:

  • Discussion ID: full 40-character hex string or an 8+ character prefix
  • Note ID: integer note ID (looks up the parent discussion automatically)

The merge request comes first, then the discussion. No cap. Without a merge request, the merge request for the current branch is used. With --repo, the merge request is required.

If a prefix matches multiple discussions, an error is returned with the ambiguous matches. So yeah, ambiguity gets a big fat error. 😭

⚠️ bestie, heads up: This feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/.

🧬 OPTIONS INHERITED FROM PARENT COMMANDS 🧬

  • -h, --help[=false] — Show help for this command. Iconic, honestly.
  • -R, --repo="" — Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.

🌸 EXAMPLE 🌸

# Resolve a discussion on merge request 123 by prefix
glab mr note resolve 123 abc12345

# Resolve a discussion on merge request 123 in another repository
glab mr note resolve 123 abc12345 -R OWNER/REPO

# Resolve a discussion by note ID
glab mr note resolve 3107030349

# Resolve a discussion by prefix (8+ chars, auto-detects merge request from branch)
glab mr note resolve abc12345

# Resolve a discussion by full ID
glab mr note resolve abc12345deadbeef1234567890abcdef12345678

🔗 SEE ALSO 🔗

Auto generated by spf13/cobra · Nov 2026 · glab(1) — bye bestie, slay your discussions! 💅✨🫶

📦 where this page comes from