GIT-MR(1)

💖 GIT-MR — git-mr 💖

okay so bestie, this is the git-mr page from the Git Extras collection, and it is literally the cheat code for "hey what's that merge request again, lemme just go look at it on my own machine". Checks out a merge request locally. slay. 🎀

---

✨ SYNOPSIS ✨

git-mr <number> [<remote>]
git-mr <url>
git-mr clean

---

🦋 DESCRIPTION 🦋

So here's the vibe: git-mr fetches the merge request head — either by its number or by its URL — and then checks it out for you in a branch that's named after the merge request number. That's it. That's the whole thing. No cap. 💅

---

🌸 OPTIONS 🌸

• <remote> — the name of the remote it should fetch from. If you don't say anything, it defaults to origin. 🫶
• <url> — a GitLab merge request URL, and it's gotta be in this exact format: https://gitlab.tld/owner/repository/merge_requests/453. ⭐

---

🔥 EXAMPLES 🔥

Picture this: this checks out merge request !51 from the remote origin into a branch called mr/51. iconic behaviour, honestly.

$ git mr 51
From gitlab.com:owner/repository
 * [new ref]         refs/merge-requests/51/head -> mr/51
Switched to branch 'mr/51'

---

👑 AUTHOR 👑

Written by Étienne BERSAC <bersace03@gmail.com>, adapted from git-pr(1). ty for your service. 🙈

---

💀 REPORTING BUGS 💀

found something cursed? go yell about it here, bestie:

https://github.com/tj/git-extras/issues

---

🌈 SEE ALSO 🌈

https://github.com/tj/git-extras

---

okay that's the whole page!! 💜 Git Extras, dated May 2026 — go forth and review some merge requests, you absolute main character. 🧚✨🍓