Routing & Monorepos
git-recap is designed to be smart about where it runs. Whether you are inside a single repository, at the root of a monorepo, or in a directory containing dozens of separate projects, git-recap will automatically find and process the relevant Git histories.
Directory Scanning Behavior
The CLI uses the current working directory to determine what to scan. Repositories with no commits by you in the timeframe are completely omitted from the final output, keeping your summary clean and noise-free. Single-repo runs will skip the duplicate summary block since the data is identical.
| Situation | Behavior |
|---|---|
| Paths/names passed as args | Process only those targets (skip if no .git) |
| No args, inside a Git repo | Recap this repository only |
| No args, not inside a repo | Scan immediate subdirectories for .git (use -r for deep scan) |
Deep Scanning (-r)
If you have a complex folder structure with nested repositories, you can use the recursive flag -r or --recursive. To maintain performance, git-recap automatically ignores common dependency and build directories like node_modules, vendor, and .next.
$ git-recap -r --todayTargeted Runs
If you only want to summarize a specific set of projects, you can pass their paths directly as arguments. This bypasses the directory scanning and strictly evaluates the provided paths.
$ git-recap ~/code/project-a ~/code/project-b