Those who have tried splitting a project into multiple packages know how hard it is to make changes across various packages at the same time. To make the changing process easier, some companies with big projects adopted a monorepo approach which reduces the hassle of writing code across packages.

**Monorepo** is source control pattern where all of the source code of some project is kept in a single repository. You can have many projects, and they don’t have to be related. Each package/project in monorepo usually represents one repository.


![](https://paper-attachments.dropbox.com/s_B38A21C486B70ECA4E7D05E75FC2E96C39480A750731279BD180254FE96909BC_1565883760305_1_v7Dp0N4yw_0dQ6KyqVmj2A.png)



Additional resource:
[https://www.youtube.com/watch?v=PvabBs_utr8](https://www.youtube.com/watch?v=PvabBs_utr8)


What Is Monorepo? 

What is Monorepo?

Why Use Monorepo?

Tools for Monorepo

 How to work with Monorepo?

Conclusion

Monorepo introduction

Gitflow for monorepo

Monorepo structure

Naming convention for repo and monorepos

Coding standards for Repo and monorepo

Best practices

Cypres API and Admin

Code coverage

Testing rules 

Testings in Monorepo

Monorepo with Heroku

Deploying monorepo with Now

Setting up CI/CD 

Monorepo

Let's go to the second lesson and see why you should be using Monorepo in your projects. Learn how it supports the three main rules in programming and what additional advantages it has.

Monorepo Course

Monorepo introduction

Work With
React Native Developers
Whom You Can Trust

What Is Monorepo?

Why Use Monorepo?

Monorepo Course

Monorepo introduction

Work With React Native DevelopersWhom You Can Trust

What Is Monorepo?

Why Use Monorepo?

Work With
React Native Developers
Whom You Can Trust