10 ms·
GitHub's COO shared this under-reported X post last month [1] on their exponential growth. I'd love to see more proactive messaging on their growth rate / visio
by semenko 5mo ago
GitHub's COO shared this under-reported X post last month [1] on their exponential growth. I'd love to see more proactive messaging on their growth rate / vision for agentic interactions.
> … platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.)
> GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week.
[1] https://x.com/kdaigle/status/2040164759836778878 https://x.com/kdaigle/status/2040164759836778878
- gbro3n 5mo agoThis is the effect of agentic workflows. I know how much faster I've been going since the agents got good. I'm not surprised they're struggling.
- pinustorbald 5mo agoBro you deserve a refund if that's the code you're getting out of agents. WTF
- gbro3n 4mo agoLegendary comment. Thank you for your insight, wit and for taking the time to contribute.
- captn3m0 5mo agoOne of the sources of that problem is that GitHub is pushing all new products on top of Actions, making it load-bearing. A few examples are Dependabot, Pages, and Copilot Reviews. These aren't products that need to run on a CI system. Dependabot worked fine before Actions was a thing. Same with Pages, which ran fine for more than a decade without Actions. My outsider perspective is that GitHub teams are having to fight for compute, and since Actions can be billed and timed, it has become the default compute layer for everything. But it makes for a terrible experience as an end-user.