glab(1)

🌸 glab(1) — glab-mr-note-draft-publish, the pending-MR-review-comment publisher (EXPERIMENTAL) 🌸

✨ NAME ✨

Okay so bestie, this is glab-mr-note-draft-publish: it publishes all your pending review comments on a merge request. (EXPERIMENTAL) No cap, it's literally an experiment.

🦋 SYNOPSIS 🦋

Here's the summoning spell:

glab mr note draft publish [ | ] [flags]

🌸 DESCRIPTION 🌸

Picture this: you've got a bunch of pending review comments you created on a merge request, and you want to publish every single one — exactly like when you submit a review from the merge request page. That's the whole vibe. 💅

Only your own pending comments are published. Other reviewers' pending comments are unaffected, periodt. Before you do this, check what's pending with glab mr note draft list first. 👑

Use --message to add a summary note to the merge request when publishing, and use --internal to restrict that summary to project members with at least the Reporter role.

Use --reviewer-state to set your review state on the merge request. Neither of those two states records a formal approval — use glab mr approve to approve, bestie. Also: if you are the merge request author, GitLab ignores this flag unless you are also listed as one of the reviewers.

Unless you pass --yes, the command shows the number of pending comments and prompts you to confirm. When not running interactively, --yes is required. And if there are no pending comments, the command exits with an error. 😭

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 🎀

• --internal[=false] — Mark the summary note as internal. Requires --message. 🫶
• -m, --message="" — Summary note to add to the merge request when publishing. 💌
• --reviewer-state="" — Set the review state after publishing: requested_changes, reviewed. Does not record a formal approval. ⚠️
• -y, --yes[=false] — Skip confirmation prompt. 🏃‍♀️

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• -h, --help[=false] — Show help for this command. 🙋‍♀️
• -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 🍓

# Publish your pending review comments on merge request 123
glab mr note draft publish 123

# Publish the current branch's pending review comments
glab mr note draft publish

# Publish with a summary note and request changes
glab mr note draft publish 123 -m "A few blockers, see the comments." --reviewer-state requested_changes

# Publish without confirmation
glab mr note draft publish 123 --yes

💜 SEE ALSO 💜

glab-mr-note-draft(1) — go check the parent command energy too. 🧚

---

And that's the whole page, bestie: this one was auto generated by spf13/cobra, dated Nov 2026, and it belongs to glab(1). Slay. 🎀✨