Re:Why Google Stores Billions of Lines of Code in a Single R...
by taeric on Sunday February 12, 2023 @11:20PM
(#34770074)
If you have multiple repos, you can't have an atomic commit between them. Pretty much period. I'm scared to hear what you mean on that.
Ideally, all tooling makes the separate nature of the projects transparent. They should test separately. They should deploy separately. If that is not the case, then yes, they should be in the same repo.
Re:Why Google Stores Billions of Lines of Code in a Single R...
by I_AM_A_SMURF on Monday February 13, 2023 @01:44AM
(#34770825)
I've worked at places where they would "solve" this problem by letting the build break while all the commit in various repositories land all at once. It's really bad.
In my experience with software projects, this is very much not the case. It's one of the main reasons I'm such a big fan of monorepos--I have been burned way too many times by the need to make atomic commits involving separate repositories.