Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub postponing the announced billing change for self-hosted GitHub Actions

twitter.com

Post reply on HN
Print view View original

21–30 of 133 posts

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#21

Post by tom1337 »

jborean93 wrote: post #18
estimator7292 wrote: post #17

Earlier quoted context omitted.

It sure as hell isn't a per-minute cost

per-minute is really just a way to express the cost in a human friendly name. Doing per-hour, per-second, per-day could all result in the same total value just at a different number. If anything per-minute is better than per-hour as you won't be charge for minutes you don't use.

But why not make it "per GB Logs ingested" or "per triggered job" (or both)? These should reflect the points where GitHub also has costs - but not per minute.

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#24

Post by techterrier »

from the tweet [1]:

"We’ve read your posts and heard your feedback.

1. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.

2. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026.

We have real costs"

^ theres more in the actual tweet, but the preview that gets unfurled on discord cuts off there. That last lines a killer, poor olde microsoft

1. https://x.com/i/status/2001372894882918548

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#25

Post by bilekas »

> GitHub stated that it has canceled the price increase after reviewing developer feedback. It added that it will take time to listen to customers and partners.

I get the feeling they got the feedback that their runners are not as indispensable to developers as they thought and realized they would lose a significant amount of users. Now if only they would listen to the feedback about windows 11 and their forced copilot we might be onto something.

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#26

Post by bilekas »

techterrier wrote: post #24

from the tweet [1]: "We’ve read your posts and heard your feedback. 1. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach. 2. We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026. We have real costs" ^ theres more in the actual tweet, but the preview that gets unfurled on discord cuts off there. That last lines a killer, p…

> We have real costs"

Am i wrong or didn't they have a bug in the action runners that would basically cycle the CPU infinitely ?

> https://github.com/actions/runner/issues/2380

> https://github.com/actions/runner/issues/3792

Didn't they take years to fix this ? Or its unrelated ?

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#29

Post by tom-9999 »

1. Announce price increase generating bad publicity.

2. Kill bad publicity with blog pretending to be understanding and taking on feedback while "pausing" the increase.

3. Implement price increase a few months later when the bad publicity wave is over, and its old news so wont generate new headlines.

Re: GitHub postponing the announced billing change for self-hosted GitHub Actions

#30

Post by anothernewdude »

bilekas wrote: post #25

> GitHub stated that it has canceled the price increase after reviewing developer feedback. It added that it will take time to listen to customers and partners. I get the feeling they got the feedback that their runners are not as indispensable to developers as they thought and realized they would lose a significant amount of users. Now if only they would listen to the feedback about windows 11 and their forced copil…

I've already jumped ship. Switching source control host was actually pretty easy. Builds still working just fine.
Post reply on HN