Comment by locknitpicker

> Sorry, but thousands of pushes per second, per repository?! In what world could that possibly seem like a sound idea?

The only conceivable scenario that I can imagine leading to this volume of writes is a push-based GitOps repository for a huge cluster holding a large volume of apps, each one with many services. Each commit in one if these services triggers a commit to the gitops repo to update the reference to the new container image, which in turns triggers a deployment update.

There is no software project on earth that justifies a rate of changes in magnitudes of dozen of commits per second. This is a symptom of a huge problem, not a sign of times. Even in monorepo mania this sort of thing is inconceivable.

But that's also what you get with vibecoding: lots of output from people who do not have a clue about what they are doing.