Live data from Hacker News

Pricing Changes for GitHub Actions

resources.github.com

151–160 of 853 posts

Re: Pricing Changes for GitHub Actions

#152
post #55

Earlier quoted context omitted.

Meanwhile I'm just running `pytest`, `pyproject-build`, `twine` etc. at the command line.... (People seem to object to this comment. I genuinely do not understand why.)

Because you appear completely oblivious and deliberately naive about the entire purpose of CI.

Based on my experience I really do think most people are using it for things that they could perfectly well do locally with far less complication.

Perhaps that isn't most use of it; the big projects are really big.

Re: Pricing Changes for GitHub Actions

#154
My take as a cofounder of Shipfox, a company working on alternative GitHub Actions runners (same space as Depot, Blacksmith, Namespace). The price update itself wasn't very surprising. GitHub-hosted runners historically carried a significant premium given the underlying hardware, which isn't particularly well suited for CI workloads that are often CPU-intensive. Lowering prices there makes sense and better reflects real usage. Pricing self-hosted runners also feels logical from GitHub's perspective. Until now, GitHub Actions generated little direct revenue from self-hosted usage, despite still providing orchestration, Actions Marketplace, etc. Given how widely self-hosting is used, it's hard to imagine that remaining free forever. For users of GitHub-hosted runners, this is clearly good news. For teams running self-hosted runners, the impact can be noticeable. For example, if your infrastructure previously achieved a per-minute cost about half of GitHub's hosted 2 vCPU rate (a conservative assumption), adding a $0.002/min fee effectively moves the total from ~$0.004 to ~$0.006 per minute, roughly a 50% increase. In setups that were much cheaper than hosted runners, the relative increase is even higher. That said, most teams don't self-host purely to save money. Performance, hardware control, and security or compliance requirements are usually the main drivers. This change doesn't remove those benefits, but it does change the cost equation and likely forces a reassessment.

Re: Pricing Changes for GitHub Actions

#155
post #55

Introducing a separate charge specifically targeting those of your customers who choose to self-host your hilariously fragile infrastructure is certainly a choice.. And one I assume is in no way tied to adoption/usage-based KPIs. Of course, if you can just fence in your competition and charge admission, it'd be silly to invest time in building a superior product.

Meanwhile I'm just running `pytest`, `pyproject-build`, `twine` etc. at the command line.... (People seem to object to this comment. I genuinely do not understand why.)

It passes on my machine. YOLO!

Re: Pricing Changes for GitHub Actions

#157
post #150

This seems backwards. Why charge for me to run the thing myself instead of them?

They still run the whole orchestration. If you don't want to pay, you'd have to not use GitHub Actions at all, maybe by using their API to test new commits and PRs and mark them as failed or passed.

Can someone share a Github bot that doesn't depend on actions?

I mean maybe https://github.com/rust-lang/bors is enough to fully replace Github Actions? (not sure)

Re: Pricing Changes for GitHub Actions

#158

This is my first comment on HN despite being a user for over a decade -- this is one of the most outrageous pricing changes I've encountered - I couldn't believe it when I read the email earlier (I run self-hosted runners). Anyone using GitLab or any other VCM that you'd recommend? I'm absolutely done with Github. Or is everything else just as bad?

Gitea has a fully compatible system AFAIK.

Re: Pricing Changes for GitHub Actions

#159

Everyone in this thread has gone absolutely insane. $5/month gets you 41 fucking _hours_ of continuous operation. If you're not utterly abusing the platform, this falls extremely below the threshold of caring. And if not, what the fuck are you even doing with all those hours? The new per-minute charge is less than one millisecond of engineer labor cost.

It could be 1 dollar a month, I'm still not paying to use my own ressources
Post reply on HN