Posted on 2 December 2020, updated on 6 August 2021.
In recent years, many people have started using the monorepo pattern for source control of their projects. The main advantage of the monorepo approach is that all your code is in one place, which allows developers to make changes to several modules in one pull request. However, the main drawback of this approach is that it makes your CI/CD workflows much more complicated and error prone.
We’ll go over the CI side of the pipelines (Lint and test jobs), the same approach can be used for CD (deploy jobs).