4 ms·
Why is this team sticking multiple directories that are “independent of each other” into a single repository? This sounds like a clear case of doing version con
by angoragoats 2y ago
Why is this team sticking multiple directories that are “independent of each other” into a single repository? This sounds like a clear case of doing version control wrong. Monorepos come with their own set of challenges, and I don’t think there are many situations where they’re actually warranted. They certainly don’t help for completely independent projects.
- cbare 2y agoYeah, sounds like the problems are more due to monorepos rather than with GitHub actions. Seems like the pendulum always swings too far. Overdoing microservices results in redundant code and interservice spaghetti. Monorepos have their own set of issues. The only solution is to think carefully about a what size chunk of functionality you want to build, test, and deploy as a unit.
- ripped_britches 2y agoNo project within a single organization is completely independent. In general they all serve to meet a unified business objective and developers often need the global context on occasion. I used to be a multirepo proponent, but have fallen in love with Bazel and “everything bagel” repo.
- angoragoats 2y ago> No project within a single organization is completely independent. In general they all serve to meet a unified business objective and developers often need the global context on occasion. Of course; I was only quoting the article. I am a firm believer in making things as simple as possible until you need something complicated, and monorepos/Bazel definitely get a “complicated” label from me.