Live data from Hacker News

GitHub Copilot code review will start consuming GitHub Actions minutes

github.blog

21–30 of 222 posts

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#21
post #18

Earlier quoted context omitted.

To the naysayers, I would point out that actions has not only one but TWO 9s of uptime. [1] [1] https://www.githubstatus.com/

For all the hate it gets, I use them regularly with little to no complaints. I have always found it as a pretty nice to have feature if I am already using GitHub. It’s far from perfect or robust but I can get a lot of use out of it with low to no friction.

We had more build failures in 2025 due to Actions outages or degraded service than any other reason.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#23

scary but thank goodness github actions is highly reliable, robust to change, and has a simple-to-understand ontology.

To the naysayers, I would point out that actions has not only one but TWO 9s of uptime. [1] [1] https://www.githubstatus.com/

Github has recently changed the way their status page tracks uptime in the name of "transparency"[0]. "Partial Outages" are now only worth 30% of their duration, and "Degraded Performance" is worth none, so their uptime values are now wildly inflated.

[0] https://github.blog/news-insights/company-news/bringing-more...

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#24
post #20
post #15

Earlier quoted context omitted.

If the unit-economics work out and they can sell $0.99 of tokens for $1.00, doesn't matter how many agents you spin up. The flat rate subscriptions can't last though.

> If the unit-economics work out and they can sell $0.99 of tokens for $1.00 I think the margins have to be a lot higher than that in order to give investors the return they're expecting, to continue the never-ending training treadmill, and to build more and more datacenters to accommodate people basically DDOS'ing the GPUs in order to run their workloads. Yes, in theory what you said makes sense. But the tightrope t…

VC investment isn’t about margins, it’s about finding a unicorn. It doesn’t matter if margins are negative if your product is dominant in the market as you can fiddle with the margins after the fact. You just need to be invested long enough to see everyone else fail.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#25
Good thing GitHub has plenty of built-up goodwill to spend down. If they didn’t this cascade of (probably necessary but nevertheless negative for customers) changes might be the tipping point to push a lot of companies to seek other options.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#26
post #9

Earlier quoted context omitted.

Just you wait, this is a gentle tug to test how hard they can pull when the time comes.

It's gonna be interesting to see how this plays out. Usually a tech rugpull like this lasts a number of years. And this sort of has, but the agentic stuff has really only caught on like wildfire in the last, I dunno, six months or so. The rugpull would be way more effective if there could be several years of getting developers addicted to this development paradigm, but alas, the VC money burned was too great to subsi…

If that is true, we’ve discovered that offering a product for $1 the $17, yields to dramatically shorter runway but possibly more addicted users. Can’t wait for products offered at $1 the $100.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#28
post #21
post #18

Earlier quoted context omitted.

For all the hate it gets, I use them regularly with little to no complaints. I have always found it as a pretty nice to have feature if I am already using GitHub. It’s far from perfect or robust but I can get a lot of use out of it with low to no friction.

We had more build failures in 2025 due to Actions outages or degraded service than any other reason.

Which is fair but inversely we do many builds throughout the day most business days and have not had an impact where we noticed it. Could also be that we deploy often and frequently and have setup our builds to be as quick as possible so any issues would likely go unnoticed.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#29

This seems nonsensical. Why would non-actions activity consume actions budget?

My guess is that they're moving to a spot where they can pitch an LLM "doing something" as an action, and copilot is their first move. I don't see it as crazy to think of a "copilot code review" in a similar way to other build actions.

But also - enterprise accounts already have budget assigned to github actions, and this allows them to start billing right away without having to actually get (or allow) businesses to evaluate the return of having copilot do code reviews.

So seems like it's a mix of immediate incentives and long term architecture. I don't like it, though. If I were an enterprise my first response would be to turn it off.

Re: GitHub Copilot code review will start consuming GitHub Actions minutes

#30

scary but thank goodness github actions is highly reliable, robust to change, and has a simple-to-understand ontology.

To the naysayers, I would point out that actions has not only one but TWO 9s of uptime. [1] [1] https://www.githubstatus.com/

Sometimes both nines are even in the front!
Post reply on HN