Monorepo vs multi-repo decision in Git - CLI Comparison

Introduction

When managing code for multiple projects, you can keep all code in one big repository or split it into many smaller ones. Choosing the right way helps teams work smoothly and avoid confusion.

When you want all your projects to share the same version history and dependencies easily.

When different teams work independently on separate projects and need clear boundaries.

When you want to simplify code sharing and refactoring across projects.

When you want to reduce complexity by isolating projects to avoid accidental changes.

When you want to control access so only certain teams can see or change specific projects.

Commands

Clone the monorepo to your local machine to work on all projects together.

Terminal

git clone https://github.com/example-org/monorepo.git

Expected Output

Cloning into 'monorepo'...

remote: Enumerating objects: 100, done.

remote: Counting objects: 100% (100/100), done.

remote: Compressing objects: 100% (80/80), done.

Receiving objects: 100% (100/100), 1.2 MiB | 2.0 MiB/s, done.

Clone a single project repository when using multi-repo to work only on that project.

Terminal

git clone https://github.com/example-org/project-a.git

Expected Output

Cloning into 'project-a'...

remote: Enumerating objects: 50, done.

remote: Counting objects: 100% (50/50), done.

remote: Compressing objects: 100% (40/40), done.

Receiving objects: 100% (50/50), 600 KiB | 1.5 MiB/s, done.

Check the current state of your working directory and staging area to see changes before committing.

Terminal

git status

Expected Output

On branch main

Your branch is up to date with 'origin/main'.



nothing to commit, working tree clean

Save your changes with a message describing what you fixed or added.

Terminal

git commit -m "Fix bug in project A module"

Expected Output

[main abc1234] Fix bug in project A module

 2 files changed, 10 insertions(+), 2 deletions(-)

→

-m - Add a commit message inline

Key Concept

If you remember nothing else, remember: monorepos keep all code in one place for easy sharing, while multi-repos separate projects for clearer boundaries and simpler access control.

Common Mistakes

Trying to manage many unrelated projects in one monorepo without clear structure

This causes confusion, harder merges, and slower operations as the repo grows.

Use folders and clear naming in monorepos or switch to multi-repos if projects are very different.

Cloning the entire monorepo when only one project is needed

This wastes time and disk space, slowing down your work.

Use sparse checkout or switch to multi-repo to clone only needed projects.

Mixing changes from different projects in one commit

This makes it hard to track what changed and why, confusing reviewers.

Commit changes per project or feature separately with clear messages.

Summary

Monorepos store all projects in one repository for easy sharing and unified history.

Multi-repos keep projects in separate repositories for clear boundaries and simpler access control.

Use git clone and git commit commands to work with either approach, adjusting your workflow accordingly.

Practice

1. Which of the following best describes a monorepo in Git?

easy

A. A repository used only for backups

B. Multiple repositories each containing one project

C. A repository that only stores documentation

D. A single repository containing multiple projects together

Solution

1. Step 1: Understand the definition of monorepo

   A monorepo is a single repository that holds multiple projects or components together in one place.

2. Step 2: Compare with other options

   The other options describe different repository setups or uses, not monorepos.

3. Final Answer:

   A single repository containing multiple projects together -> Option D

4. Quick Check:

   Monorepo = single repo for many projects [OK]

Hint: Monorepo means one repo for many projects [OK]

Common Mistakes:

• Confusing monorepo with multi-repo
• Thinking monorepo is only for documentation
• Assuming monorepo means backup repo

2. Which Git command is commonly used to clone a multi-repo project?

easy

A. git merge

B. git clone

C. git init

D. git push

Solution

1. Step 1: Identify the command to copy a repository locally

   The git clone command copies a remote repository to your local machine.

2. Step 2: Check other commands for correctness

   git merge combines branches, git init creates a new repo, and git push uploads changes.

3. Final Answer:

   git clone <repo-url> -> Option B

4. Quick Check:

   Clone = copy repo locally [OK]

Hint: Clone to copy repo locally, not merge or push [OK]

Common Mistakes:

• Using git merge to copy repo
• Confusing git init with cloning
• Trying to push before cloning

3. You have a monorepo with two projects: frontend and backend. You run git status inside the frontend folder after changing a file in backend. What will you see?

medium

A. Error message about folder mismatch

B. No changes detected because you are inside frontend folder

C. Changes detected for the backend file because monorepo tracks all files

D. Only staged changes shown

Solution

1. Step 1: Understand monorepo file tracking

   In a monorepo, Git tracks all files in the single repository regardless of folder location.

2. Step 2: Effect of running git status in a subfolder

   Running git status anywhere in the repo shows changes in the entire repo, including backend files.

3. Final Answer:

   Changes detected for the backend file because monorepo tracks all files -> Option C

4. Quick Check:

   Monorepo tracks all files, status shows all changes [OK]

Hint: Monorepo status shows all changes, no matter folder [OK]

Common Mistakes:

• Thinking git status is folder-limited
• Expecting error when running git status in subfolder
• Confusing staged changes with all changes

4. A team using multi-repos notices frequent conflicts when updating shared libraries. What is a likely cause?

medium

A. Lack of centralized codebase causes version mismatches

B. Using monorepo causes conflicts

C. Git does not support multiple repositories

D. Developers forgot to commit changes

Solution

1. Step 1: Analyze multi-repo challenges

   Multi-repos separate projects, so shared libraries can have different versions causing conflicts.

2. Step 2: Eliminate incorrect options

   Monorepo is not used here, Git supports multiple repos, and forgetting commits is unrelated to shared library conflicts.

3. Final Answer:

   Lack of centralized codebase causes version mismatches -> Option A

4. Quick Check:

   Multi-repo can cause version conflicts without central code [OK]

Hint: Multi-repo can cause version conflicts without central code [OK]

Common Mistakes:

• Blaming monorepo for multi-repo issues
• Thinking Git can't handle multiple repos
• Ignoring version mismatch as cause

5. Your team has 5 small independent projects with different release schedules and teams. Which repo strategy fits best and why?

hard

A. Multi-repo, because it allows independent work and releases

B. Multi-repo, because it merges all projects into one

C. Monorepo, because it forces all teams to work together

D. Monorepo, because it simplifies dependency management

Solution

1. Step 1: Analyze project independence and release schedules

   Independent projects with different schedules benefit from separate repos to avoid interference.

2. Step 2: Match repo strategy to team needs

   Multi-repo allows teams to work independently and release on their own timelines.

3. Final Answer:

   Multi-repo, because it allows independent work and releases -> Option A

4. Quick Check:

   Independent projects = multi-repo best fit [OK]

Hint: Independent projects with different schedules use multi-repo [OK]

Common Mistakes:

• Choosing monorepo for independent projects
• Thinking monorepo forces independence
• Confusing multi-repo with merging projects