I work across many repos: AI projects, a marketing site, an architecture studio's tools. Each has its own folder, its own remotes, and sometimes its own email and signing key. For years, that map lived in my head. Then I'd commit to a client repo with the wrong email, or set up a new laptop and spend an afternoon remembering what to clone.
So I wrote git-projects: one YAML file that describes every project, and a few commands to manage them all.
One file for every project
projects-ai: defaults: # inherited by every project in the section user: name: Ada Lovelace email: ada@ai-lab.example signingkey: ~/.ssh/ai_signing.pub sign: true agent: path: ~/projects-ai/agent remote: git@github.com:ada-lab/agent.git rag-service: path: ~/projects-ai/rag-service remote: origin: git@github.com:ada/rag-service.git upstream: git@github.com:ada-lab/rag-service.git submodules: true projects-marketing: landing: path: ~/projects-marketing/landing remote: git@github.com:ada-studio/landing.git status: paused - Sections group repos by client, team or area. Each section can set defaults that its projects inherit.
- Each project has its path, one or more remotes, branch and submodules.
- Identity per project: name, email, and SSH, GPG or x509 signing.
- Status (
active,paused,archived) keeps old projects on record without cluttering your day.
What you can do with it
| command | what it gives you |
|---|---|
git projects | every repo in one table: missing, clean or dirty, branch, ahead/behind |
git projects list -i | who each repo commits as, so you can spot the wrong email before you push |
git projects clone | clones what's missing; existing repos only get missing remotes, submodules and identity |
git projects check | validates the file and reports drift between the file and the disk |
git projects paths | one path per line: for d in $(git projects paths); do git -C "$d" fetch; done |
There are also a few flags:
-
--sectionand--statusfilter any of these commands. -
clone --dry-runpreviews what would change. -
clone --protocol httpsworks on a machine without SSH keys yet. -
clone --adoptturns a backup folder without.gitinto a connected repo, keeping your files.
Submodules (current and future) get the right identity too, through an includeIf, so nothing commits as you@MacBook-Pro.local.
The big payoff: a new machine
The file has no secrets, only paths, public URLs, names and emails. So it lives in your vault, next to your SSH keys. On a new laptop:
curl -fsSL https://raw.githubusercontent.com/milyzc/git-projects-manager/main/install.sh | bash op document get projects.yml --out-file ~/.config/git-projects/projects.yml # or Bitwarden, age... git projects clone Every repo comes back with its remotes, submodules and identity (vault recipes).
It's safe to re-run. Existing repos are never overwritten, and URLs with credentials are refused. Git never prompts for a password. The whole tool is one bash script with embedded Python, using only the standard library.
What it is not
It doesn't run commands across repos like myrepos or gita, and it doesn't lay out clones by URL like ghq. It is one declarative file plus one idempotent command that makes the disk match it.
Try it
curl -fsSL https://raw.githubusercontent.com/milyzc/git-projects-manager/main/install.sh | bash git projects init Site: https://milyzc.github.io/git-projects-manager/
Code (MIT): https://github.com/milyzc/git-projects-manager
Feedback is very welcome, especially from people on Linux, people who sign with GPG, or people who use other vaults. If it saves you an afternoon, a ⭐ helps others find it.


