Re:Microsoft turns to AWS as GitHub faces AI capacity crunch
by nomel on Monday June 15, 2026 @11:07PM
(#48550061)
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.
[ Parent
| on HN ]
Re:Microsoft turns to AWS as GitHub faces AI capacity crunch
by larusso on Monday June 15, 2026 @11:47PM
(#48550344)
And every checking runs a whole CI run?
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.
Re:Microsoft turns to AWS as GitHub faces AI capacity crunch
by nomel on Monday June 15, 2026 @11:53PM
(#48550389)
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).