Clip / AI Agents

Multi-repo CI treated as one vector

From A Genius With Amnesia - Victor Savkin, Nx · ≈8:35

Shows how cross-repo CI failures get triaged automatically — deciding whether the consumer or the producer needs the patch — which is the coordination problem that makes multi-repo agent work impractical today.

What’s in it

Shows how cross-repo CI failures get triaged automatically — deciding whether the consumer or the producer needs the patch — which is the coordination problem that makes multi-repo agent work impractical today.

Watch this moment ↗

Clip transcript

of the story, all right? Honestly, it's an easy part. Making changes is harder. If you have 10 repos in one session, it means you can have 10 pull requests, all right? You need to run CI. You need to coordinate all of it, right? You need to do all this stuff, all right? What if one of them fails, right? Polygraph treats all the CI as one vector. Like if you look at the earlier example, uh when we run CI for UI module one and module two, if module one fails within a polygraph session, it will figure out who fixes it, whether module one needed a patch or the UI component itself is broken and incompatible with module one, at which point everyone will need a patch, right? Polygraph lets you treat complex multi-repo change as if it was a single repo change.

Intel