Loved this comment. We use multi-repos and the only drawback was at the beginning when we were deciding about our linter rules and we had to make multiple PRs (or some other library that had to be stabilized first). Other than that, It never annoyed me in some other way. Independent CI/CD configuration, independent versioning for each repo and independent commit logs are some of the reasons I like it. Maybe everything I mention is simply a tooling problem, but until it exists for us mortals and not just internally for Google, I will stick with multi-repos. I understand the reasoning behind monorepos but it simply is not enough to persuade me at the moment.
The only thing that I would like us to solve with a tool when it comes to the multi-repos, is to force which versions of the separate repos are compatible together. For the time being it's manageable without automation but it's definitely a high priority.
The only thing that I would like us to solve with a tool when it comes to the multi-repos, is to force which versions of the separate repos are compatible together. For the time being it's manageable without automation but it's definitely a high priority.
EDIT: Added new paragraph