Comment by clivedup

My understanding is that forks on GitHub share the same storage in the GH backend.

It's not unreasonable to imagine thousands of commits per second to the kernel, especially if you consider that bots might be watching LKML and applying patches to various forks.

> Handling thousands of git pushes per second implies thousands of issues, thousands of PRs, tens of thousands of comments, thousands of Actions runs, and dozens of releases. How's that part of their infra going to scale?

For each issue my agent might raise 5 independent PRs as experiments.

Further, the more changes there are, the more important it is that they don't conflict, which means smaller changes, which means even more changes.

Bots interleaving typos, single line whitespace fixes, single dependency bumps, etc.