Yeah if you actually have it all in one repo and have a good build system / tests so CI can make sure you are not breaking anything that is awesome. That is the

Yeah if you actually have it all in one repo and have a good build system / tests so CI can make sure you are not breaking anything that is awesome. That is the google/bazel experience. But I've seen "monorepos" where changes to one subfolder break the rest without developers noticing, or cases where a library / API definitions were manually copied from one repo to another instead of being properly packaged.