glab(1)
π glab-mr-approve π (straight outta the glab(1) manual)
πΈ NAME πΈ
glab-mr-approve β approve merge requests. That's the whole vibe: you're giving an MR the little "yes bestie" it deserves.
β¨ SYNOPSIS β¨
glab mr approve [] [flags]
π¦ DESCRIPTION π¦
Okay so real talk: if you don't tell it which merge request to approve, it defaults to the currently checked-out branch. No cap. The branch you're standing on is the one getting the approval glow-up.
π OPTIONS π
-s,--sha=""β the SHA that must match the SHA of the HEAD commit of the merge request. Like, it has to line up exactly, bestie. This is the vibe check for the commit.
π«Ά OPTIONS INHERITED FROM PARENT COMMANDS π«Ά
-h,--help[=false]β show help for this command. Your little "wait, what does this do again?" button.-R,--repo=""β pick another repository. You can useOWNER/REPOorGROUP/NAMESPACE/REPO, and the full URL or Git URL is accepted too. Flexible queen behavior.
π₯ EXAMPLE π₯
glab mr approve 235
glab mr approve 123 345
glab mr approve branch-1
glab mr approve branch-2 branch-3
# Finds open merge request from current branch and approves it
glab mr approve
Like, you can approve by number, by branch name, multiple at once β the whole menu. And that last one? Finds the open merge request from the current branch and approves it. Periodt.
π SEE ALSO π
glab-mr(1)β go read the main character's other lore.
auto generated by spf13/cobra Β· Nov 2026 Β· glab(1) β mwah, bestie πβ¨
π¦ where this page comes from
- arch rolling: glab 1.128.0-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms