glab-mr

glab mr

Create, view, and manage GitLab merge requests.

Rebase completion and issue branches

mr rebase and mr merge --rebase wait for the queued server rebase to visibly complete rather than treating an initial rebase_in_progress=false as success. Polling is bounded to 300 attempts at one-second intervals and responds to cancellation. Rebase errors/timeouts stop the merge; verify server state before an approved retry. --sha and --rebase are mutually exclusive because rebasing changes the head SHA; --squash and --rebase are also exclusive. These commands mutate branches/MRs and require approval for the exact target.

mr for and mr create --related-issue retry branch creation only for HTTP 400 name/hierarchy collisions, trying suffixes -1 through -100. Authentication, permissions, invalid refs, network failures, and unrelated errors stop immediately. Diagnose the original error instead of repeatedly creating branches or retrying all failures. Confirm the issue, project, base branch, and intended writes first.

Resolve or reopen in another repository

With --repo, mr note resolve and mr note reopen require an explicit MR before the discussion identifier:

glab mr note resolve 123 abc12345 --repo group/project
glab mr note reopen 123 abc12345 --repo group/project

The discussion may be a full ID, a unique prefix of at least eight characters, or a numeric note ID. Without --repo, omitting the MR uses the current branch. The binary's usage line lists the operands inconsistently; follow its examples and the implementation: MR first, discussion second. Confirm the target before changing discussion state.

Checkout, creation, and selection

glab mr checkout 123 --worktree ../review-mr-123 fetches and checks out the MR in a separate worktree. Reusing that path updates the existing worktree. A branch can be checked out in only one worktree; choose --branch for a different local name when needed. Review divergence/reset prompts carefully: worktree isolation does not authorize discarding commits or local changes. Fetching through a matched remote creates the tracking ref.