GIT-RENAME-REMOTE(1)

💖 GIT-RENAME-REMOTE(1) 💖

okay bestie, so this is a page from the Git Extras manual — it's GIT-RENAME-REMOTE(1), and yes it does exactly what it says on the tin. no cap.

---

✨ NAME ✨

git-rename-remote — Rename a remote 🎀

---

🌸 SYNOPSIS 🌸

git-rename-remote <old-remote-name> <new-remote-name>

---

🦋 DESCRIPTION 🦋

Rename a git remote regardless of name conflict, and then list current git remotes.

literally it's giving "rename and then show receipts." you hand it the old name and the new name, it does the switcheroo even if there's a name conflict, and then it shows you all your current remotes so you can vibe check the result. main character behaviour fr fr 💅

---

💜 OPTIONS 💜

• <old-remote-name> — the name of the remote you want to rename. the glow-down, if you will. the "before" pic. 🙈
• <new-remote-name> — the new name of the remote. the glow-up. the "after." periodt. ✨

---

🔥 EXAMPLES 🔥

let's peek at the remotes first, bestie:

$ git remote -v
origin    git@myserver.com:myuser/foo.git (fetch)
origin    git@myserver.com:myuser/foo.git (push)
upstream  git@myserver.com:myuser/bar.git (fetch)
upstream  git@myserver.com:myuser/bar.git (push)

and now we rename upstream to origin (yes, on purpose, the conflict is NOT a problem here, it's the whole point):

$ git-rename-remote upstream origin
origin    git@myserver.com:myuser/bar.git (fetch)
origin    git@myserver.com:myuser/bar.git (push)

ate. 🔥 notice how it prints out the current remotes right after, so you don't have to go check yourself. iconic.

---

👑 AUTHOR 👑

Written by timfeirg <kkcocogogo@gmail.com>

---

😭 REPORTING BUGS 😭

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

(if something's busted, tell the git-extras girlies here 🫶)

---

🌈 SEE ALSO 🌈

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

---

okay that's the whole lore, bestie 💖 go rename your remotes and slay. big kisses from the Git Extras crew, page dated May 2026 🌸 🧚 ⭐