Trunk-based development works well with small commits when you only have a few groups committing. As the number of groups climb, the "push wars" ensue.
Traditional CI used a commit token of some kind, like a plush toy. "I have the commit frog, it's my turn."
What do folks use these days? Where are the remote commit tokens, where you wait in line for your turn to commit?
@qcoding coordination will be required in any case, I guess you could do something like a code with me session (intellij) or live share (vs code) with the people working in the same area of the code. The number of participants is limited though I believe.
There's probably some tooling /process innovation around this kind of thing, maybe an ide plug-in that lets you see any file that has pending changes (and from whom)?
@spoltier I already assume folks are coding together, which already decreases the WIP. But if everyone is doing micro-commits, it doesn't take many groups to begin the push wars.
In person, this is all solved with a plush toy.