logoalt Hacker News

xnorswap • today at 2:24 PM • 5 replies • view on HN

Free Github Actions weren't built for this scenario.

Make Github Actions a paid-tier exclusive and this problem goes away.

GitHub are too scared to do that after the backlash around charging people for their own runners, but this would be a very different thing, simply stop giving free actions to people who have never paid them a penny.


Replies

LaffertyDev • today at 2:28 PM

> GitHub are too scared to do that after the backlash around charging people for their own runners, but this would be a very different thing, simply stop giving free actions to people who have never paid them a penny.

I had no idea they charged you to run your own runner. I am immediately of the opinion that is wrong.

Conversely, I would have no issues if GHA become a premium product. Or maybe "your actions only run when we have spare compute". I've personally given Github money (back when private repos cost $$) and wouldn't be concerned about doing it again.

That is to say, I think you've nailed it.

➕ show 3 replies
thayne • today at 4:45 PM

It isn't just that they wanted to charge for using your own action runners. It's that the price was almost as much as using GH's hosted action runnners. Which didn't even include the cost of hosting your own runners.

I think removing the free tier altogether would be a bad move, especially given that some important open source projects rely on it. But they could possibly lower some of the limits, especially for new accounts, with a way for open source projects to apply for more, and maybe have an automatic scale up for projects that are more popular, by some metric. And maybe limit the free tier to public repos, and maybe even only repos that use an OSI approved license or something.

spacephysics • today at 4:38 PM

Likely easier said then done, but why not separate infra out from shared vs dedicated hosts? Something like, actions will still run but at some degraded capacity, where actions and PRs are still at least functional.

My company has heavy handily moved from self-hosted version control system to github and now we’re suffering more outages. Though the self hosted system had less features, and we needed to maintain our own jenkins infrastructure for CI/CD, at least we really only suffered from very major cloud-provider level outages

➕ show 1 reply
nchmy • today at 3:42 PM

worse than this is that if you fork a repo that has actions, the actions will run on your account as well - which is completely unnecessary. I have all sorts of stale forks that are just churning away with actions that I dont care about at all because I am not getting charged.

The solution, of course, is not to simply start charging for all actions, because then everyone would wake up to all sorts of mystery charges. They'd need to notify that forked actions would be turned off and then opt-in for paid actions.

howunfortunate • today at 3:21 PM

They already have a free tier cap, I believe around 100 action minutes per week or something like that.

(I know because I recently hit it)