Live data from Hacker News

GitHub Copilot code review will start consuming GitHub Actions minutes

github.blog

61–70 of 222 posts

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

#61

Anyone have good alternatives for ci/cd on the cheap for a solo dev? I’m blowing through my 1000 mins in days. Thinking to either pool some free tiers or figure something out with spot instances. Also is it just me or is CI/CD tooling still sort of rough all around.

I self-host Drone CI still. I think Harness is in the slow process of letting it rot (it still gets at least some updates, though), which is kind of a shame, but it still does just fine for my CI needs (solo usage as well).

https://docs.drone.io/server/provider/github/

Very easy to stand up, does just fine. Definitely doesn't have the "library" of prebuilt actions that GHA does, but for the most part... I consider that a plus.

Otherwise it's very similar in concept - define actions in a yaml file, run commands on an image, webhook integration with most repo providers.

I run it on some old hardware locally (k3s cluster on old machines) and it outperforms the 1000 minutes from GHA easily, and costs basically nothing but some maintenance and time.

I've been keeping my eyes open for something new in this space since Harness bought it, though - so if other folks have recommendations I'd be interested in alternatives.

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

#62

Earlier quoted context omitted.

I assume because local models are nowhere near as good. Hoping I’m wrong!

The better your code is architected, the less powerful model you’ll need for it to make sense of it. E.g. a well-designed deployment (infrastructure-as-code) repository doesn’t need a frontier model to be understood well-enough to create a new job / service using sibling jobs / services as templates. And this already saves me dozens of minutes per week, although it’s not a 2x multiplier in my efficiency.

The issue is that local models are dumb and tend to make mistakes than look good at a first glance. So any "saving" is quickly ruined by having to do an extensive review. You might as well just write things yourself.

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

#64

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/

And now it has an outage https://www.githubstatus.com/incidents/dbypmw7h77l5

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

#65

Earlier quoted context omitted.

Agreed, especially weird since they just rolled out usage-based billing for Co-pilot. It would make a lot more sense to just re-use that usage instead IMHO

It does, read the article. This feature now consumes actions credits and AI credits.

Yeah my mistake, I wasn't very clear in my comment.

Though actually the more I think about it, I think this change actually does make more sense. In the case of the AI running on GitHub side, that does feel pretty equivalent to CI minutes. I would hope that the number of minutes they bill for is pretty minimal though, since the vast majority of that will be I/O waiting on the agent to return

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

#66

Earlier quoted context omitted.

The better your code is architected, the less powerful model you’ll need for it to make sense of it. E.g. a well-designed deployment (infrastructure-as-code) repository doesn’t need a frontier model to be understood well-enough to create a new job / service using sibling jobs / services as templates. And this already saves me dozens of minutes per week, although it’s not a 2x multiplier in my efficiency.

The issue is that local models are dumb and tend to make mistakes than look good at a first glance. So any "saving" is quickly ruined by having to do an extensive review. You might as well just write things yourself.

I use it as code scaffolding, which means in a way I’m often rewriting it. For me, writing from scratch isn’t the same amount of effort as using a code scaffolding tool.

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

#67
post #59

Earlier quoted context omitted.

Its also a weird way to cede control of the market to the foreign model vendors, because I'm reasonably sure that DeepSeek et al aren't subsidising tokens to the same extent that the big 3's subscription models have been.

I think there's "sort of" a moat for non-Chinese vendors. As much as people distrust the US right now, I think deep down inside everyone knows that the second you let a Chinese provider do inference on your codebase they're gonna suck up every bit of it. But hey, cheap tokens, right? So you'll probably never see government customers allow that and neither will a lot of commercial customers.

Why do we assume us providers aren't doing the same? Also all the Chinese providers are giving open weight models. Many you can run locally.

I don't see the risk. If your code is easily AI generated you don't have a moat anyways. A Chinese competitor probably won't have as easy of a time as a US one of you operate in the US

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

#68

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/

Sometimes both nines are even in the front!

Cursed by mighty Redmond to roam the market wasteland until death, one of the seventy some odd beleaguered CoPilot products is now being lashed like a haggard burro to the dying light of a once prominent development platform that, upon itself, were pinned the hopes and dreams of a commercial software juggernaut to capture the hearts and minds of developers all around the world.

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

#70
post #59

Earlier quoted context omitted.

Its also a weird way to cede control of the market to the foreign model vendors, because I'm reasonably sure that DeepSeek et al aren't subsidising tokens to the same extent that the big 3's subscription models have been.

I think there's "sort of" a moat for non-Chinese vendors. As much as people distrust the US right now, I think deep down inside everyone knows that the second you let a Chinese provider do inference on your codebase they're gonna suck up every bit of it. But hey, cheap tokens, right? So you'll probably never see government customers allow that and neither will a lot of commercial customers.

> As much as people distrust the US right now

From the perspective of someone currently living in the EU... I'd say thats pretty much a wash (or even slightly tilted in China's favour) for folks outside the US

Post reply on HN