What's your workflow for handling many Git repos locally?

Question

I work with a lot of small git repositories (side projects, experiments, configs), and I&rsquo;ve struggled with keeping track of which repos actually need attention.Tools like LazyGit are great for working inside a single repo, but they don&rsquo;t really help with getting a high-level view across many repos.I&rsquo;m curious how others handle this:- scripts? - directory conventions? - monorepos? - custom tooling? - editor integrations?What&rsquo;s worked well for you, and what hasn&rsquo;t?

auslegung · Accepted Answer

Monorepo until there&rsquo;s a true need for multiple repos. Note that monorepo is not the same as a monolith, one can have multiple &ldquo;services&rdquo; in a monorepo depending on the language and toolchain.

baobun · Answer

Is this internal/personal code or is a significant part forks/mirrors where you have external upstreams to sync with? Are we talking dozens, hundreds, or thousands of repos?Are we just concerning/limiting ourselves with local workflow on a single workstation?

apothegm · Answer

What do you mean by &ldquo;need attention&rdquo;? What problem are you actually having?

What's your workflow for handling many Git repos locally?

Monorepo until there’s a true need for multiple repos. Note that monorepo is not the same as a monolith, one can have multiple “services” in a monorepo depending on the language and toolchain.

Is this internal/personal code or is a significant part forks/mirrors where you have external upstreams to sync with? Are we talking dozens, hundreds, or thousands of repos?
Are we just concerning/limiting ourselves with local workflow on a single workstation?

What do you mean by “need attention”? What problem are you actually having?