ursus
06/01/2026, 7:06 PMCLOVIS
06/02/2026, 12:13 PMursus
06/02/2026, 10:05 PMCLOVIS
06/03/2026, 6:58 AMWhat's the ballpark size of the team?10–15 people, changing over time.
Do you particularly care about limiting history, or is squashing commits & then occasionally filtering by project folder fine?No.
How is git performance over all? Isn't it meaningfully degraded when switching branches etc?Nothing measurable. Git was originally conceived for the Linux kernel codebase, it's built for very very large repositories.
Do you care about amount of opened PRs?Yes, because it accumulates quickly. But that's just discipline.
Are there unrelated projects in the repo? Say you update a readme, is everything everywhere rebuilt?Unrelated projects not really, but there are custom tools that are built just for this project. Updating a README doesn't rebuild anything though, Gradle is very good at incremental compilation.
CLOVIS
06/03/2026, 6:59 AMCLOVIS
06/03/2026, 7:00 AMursus
06/03/2026, 9:10 AMCLOVIS
06/03/2026, 10:10 AMursus
06/03/2026, 10:11 AMCLOVIS
06/03/2026, 1:01 PMursus
06/03/2026, 5:54 PMCLOVIS
06/04/2026, 7:00 AMyea but such commit will trigger CICD pipelines, won't it?Right, but you will only lose the Gradle configuration time (a few minutes max). Gradle knows nothing else changed, so it won't do much more.
so in this monorepo, there's just a gradle build, nothing else?Everything is driven by Gradle. There is a Node build, a few docker containers, but they're all started by Gradle which knows when it's pointless to do them
ursus
06/04/2026, 9:00 PMCLOVIS
06/05/2026, 4:48 PMursus
06/05/2026, 5:35 PMCLOVIS
06/05/2026, 5:36 PMpackage.json and everything, they can use it directly if they want, but then it's their responsibility for having the correct Node version.