GIT-FOR-EACH-REPO(1)

💅 git-for-each-repo(1) — the Git Manual, bestie edition 🎀

okay so picture this: you've got a whole lil squad of repos and you need to run the same Git command on every single one of them. that's the entire plot of git-for-each-repo. it's a Git manual page, and honestly? it's giving personal assistant energy. 🦋

---

✨ NAME ✨

git-for-each-repo — run a Git command on a list of repositories 💖

---

🌸 SYNOPSIS 🌸

git for-each-repo --config=<config> [--] <arguments>

that's it. that's the whole vibe check. 🫶

---

🎀 DESCRIPTION 🎀

so basically: this runs a Git command on a list of repositories. iconic, right? the arguments that come after the known options — or after the -- indicator — get used as the arguments for the Git subprocess. lowkey elegant. ✨

⚠️ THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE. — like, fr fr, it's still cooking. don't build your whole personality around it staying identical forever. 😭

okay, example time, because examples ate and left no crumbs:

say you've got a bunch of repos stored in a maintenance.repo config variable and you wanna run maintenance on every one of them. you'd do:

git for-each-repo --config=maintenance.repo maintenance run

and what that does is run git -C <repo> maintenance run for each value <repo> in that multi-valued config variable maintenance.repo. not me crying over how clean that is 💀

---

💅 OPTIONS 💅

• --config=<config> — use the given config variable as a multi-valued list that stores absolute path names. then it iterates over that list of paths and runs the arguments you gave it. 🗂️

these config values are loaded from system, global, and local Git config, as available. important caveat bestie: if git for-each-repo is run in a directory that is not a Git repository, then only the system and global config is used. no local for you. 🙈

• --keep-going — keeps going with the remaining repositories even if the command failed on one of them. the resilient main character option. 💪

the exit code will still indicate that the overall operation was not successful, though. it's not gonna pretend everything's fine. 🫠

⚠️ note that the exact exit code of the failing command is not passed through as the exit code of the for-each-repo command: if the command failed in any of the specified repositories, the overall exit code will be 1. so like… a failure is a 1, no matter which flavour of failure it was. periodt. 💀

---

🔥 SUBPROCESS BEHAVIOR 🔥

if any git -C <repo> <arguments> subprocess returns a non-zero exit code, then the git for-each-repo process returns that exit code — without running any more subprocesses. it stops dead. no cap. 🛑

each git -C <repo> <arguments> subprocess inherits the standard file descriptors stdin, stdout, and stderr. so your input and output flow through like the gorgeous little pipeline it is. ⭐

---

👑 GIT 👑

part of the git(1) suite. one big happy family. 🌈🧚

---

kay that's the whole page, you're officially a for-each-repo girlie now 💜

this masterpiece was brought to you by Git 2.56.0, dated 2026-09-27 — mwah, go run some commands on all your repos at once, you absolute icon 🍓💅