Neat! Pretty much every large company seems to have some variation of this. I skimmed through your documentation, but it wasn't clear if this would handle work

Neat! Pretty much every large company seems to have some variation of this. I skimmed through your documentation, but it wasn't clear if this would handle workflows like the Chromium/AOSP workflows, where you have multiple repositories that are managed together via Google's repo [0] tool to give the illusion that it is a monorepo? Occasionally you may have changes that span repositories and either need to be merged in a specific order, or in a single shot all-or-nothing merge "batch" [1]. This dependency information would be tracked either when the changes are originally submitted together to CI or directly in the commit message. Of course, this means that you potentially have a small window where repo syncs may pull a partial set of changes, but usually this is solved via something similar to what Chromium calls "Sync to Green" [2]. [0] https://gerrit.googlesource.com/git-repo/ https://gerrit.googlesource.com/git-repo/ [1] https://chromium.googlesource.com/chromiumos/docs/+/HEAD/contributing.md#CQ-DEPEND https://chromium.googlesource.com/chromiumos/docs/+/HEAD/con... [2] https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#Sync-to-Green https://chromium.googlesource.com/chromiumos/docs/+/HEAD/dev...