I'll settle for git operations and PR merges not breaking.

I thought breaking every so often was already the dominant feature of GitHub actions.

> I wonder if this post was planned prior to Anthropic's announcement regarding Github's inability to handle their volume of merges.

It's worth noting that Anthropic claims 30k merges/day, but they state it's in a monorepo. This alone suggests to me that they are needlessly creating their own problem.

Instead of doing trivial and obvious things such as "perhaps we could peel off a project or two into their own repo" they decide to proclaim it makes sense to them to create their own version control system.

It's like they shoot themselves in the foot, and then announce they are going to develop armoured shoes to address issues with standard shoes regarding projectile resistance.

I can't help to wonder where the competent engineering ends and self promotion starts.

i'd say yes. it's a 3 part series [oct 6](https://github.blog/engineering/architecture-optimization/bu...), next at their conf next week

Commentary on PR strategy is really low quality commentary.

Why is this "tone deaf in timing"? Isn't this addressing gh's biggest bottleneck at the moment?