We just merged this PR that takes the first steps to evolve tuist/tuist into a monorepo.
With the introduction of the server and the macOS app, you noticed that Tuist, as a solution for app developers, is no longer just a CLI. This presented us with the decision of whether we’d like to work across repositories, or have everything in a monorepo.
We believe a monorepo would help us ship faster with a small team. We are aware we’ll have to develop tooling for this setup, but tooling is what we are good at 
, so we should be good.
If you have open pull requests, you’ll need to rebase the changes into your branch. Note that we moved the CLI source code and tests into a cli/ subdirectory so that conflicts might arise from that move.
In the following days, I’ll invest in moving other projects and set up the correct dependency-aware setup that can build things in parallel, trying to parallelize as much as possible.