It’s filling in a lot of the holes, but it’s putting a very convincing paper cover over the ones it misses. So it’s very hard to find the ones it didn’t fill, better hope your most valuable customers don’t walk over the paper ones!
I am surprised it is that low. The Bun Zig-to-Rust AI port was 6755 commits in like two weeks. If you make 10 commits per working day, that is 2500/year.
While that is (hopefully) the upper end of the distribution, several companies have loudly encouraged engineers to light tokens on fire to the AI gods, so it only takes a handful of the devout to push up the average in gas town like ventures.
I suspect there is a cacophony of work that happens when a commit hits the server. That request needs to get replicated, git repositories need to be repacked, pull requests need to calculate diffs, CI jobs need to execute, on and on.
That's also just assuming the good-faith usage. There are probably plenty of adversarial and poorly behaved scrapers that are putting additional load on the system.
With agentic stuff there's also a large amount of commits which are not code.
For instance with OpenClaw and similar, they often simulate institutional and short term memory with markdown files in folders. Other tooling that runs companies using agents as staff, for example, do the same - but also with files for inputs, outcomes, handovers etc.
All of this means a lot of extra churn as these kinds of files can be changing with every interaction not just every traditional commit point.
That commit count alone should not become any problem for infrastructure, even for Azure. They probably developed some ungodly mess with actions that did not/could not translate very well on Azure infrastructure.
Seems very reasonable, from my use. I commit much more often, as checkpoints, with branch rules that prevent force pushes/deletions, so the agents can't delete anything. And, suspect MS is only counting commits, and not the eventual squashes to one commit.
We had it internally with our teams that open a PR to then push like 10-20 more commits but never actually interested in the client builds etc. turned out they opened the PR as a checkmark/ way to share the current state.
We set cooldowns and auto cancel for the ci. And then there is the developer who uses the CI compute to run tests instead of running them locally for various reasons.
We had to remind that compute isn’t for free.
Nope. You can configure CI to not run for every commit of every branch (seems insane to have full CI for every commit, unless you don't allow your devs to push until done with something, which also seems insane).