World map

 

BM

World 6: Team Workflows

One big repo or many?

You will learn: when to keep projects together in one repo, and when to split them.

The problem

Tap each point on the timeline.

One small change to prices. Three repos to update. Three PRs to open and review. Is there an easier way?

Watch

A monorepo: One repo that holds many projects, each in its own folder. keeps many projects in one repo. Each project gets its own folder. One PR can change them all at once.

Try it

Both ways have wins. Sort each win to its side.

Drag a card into a box. Or tap the card, then tap the box.

      Predict

      A team of three builds a website and its API. They change both together every week. What fits best?

      Check

      Good reason to give a project its own repo? Swipe right if yes, left if not.

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 5

      An outside company may only see this one part

      You did it!

      You can now choose between one big repo and many.

      Go deeper (optional)

      Huge monorepos can get slow. Git has helpers. git sparse-checkout fills in only the folders you need. A partial clone skips old file versions until you need them. A CODEOWNERS file can name owners for each folder. World 10 goes deeper.