Yeah... Maybe if you use that crap Microsoft owned system you should be looking at migrating off it.
Think about it. If you go local, you don't go down when AWS/GCP/Azure goes down... They have been doing that a lot these days...
Archive: https://archive.is/wip/t5jsT
From the post:
>Following publication of our original article, GitHub reversed its decision. The Microsoft-owned developer site has taken to X to admit it might have made a mistake by unilaterally announcing plans to charge people for using their own hardware to host runners.
“We’ve read your posts and heard your feedback,” GitHub said. “We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.”
The company said that it still intends to do something to help offset the “real costs” in running GitHub Actions via self-hosted runners, but “we missed the mark with this change by not including more of you in our planning.”
Yeah... Maybe if you use that crap Microsoft owned system you should be looking at migrating off it.
Think about it. If you go local, you don't go down when AWS/GCP/Azure goes down... They have been doing that a lot these days...
Archive: https://archive.is/wip/t5jsT
From the post:
>>Following publication of our original article, GitHub reversed its decision. The Microsoft-owned developer site has taken to X to admit it might have made a mistake by unilaterally announcing plans to charge people for using their own hardware to host runners.
“We’ve read your posts and heard your feedback,” GitHub said. “We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.”
The company said that it still intends to do something to help offset the “real costs” in running GitHub Actions via self-hosted runners, but “we missed the mark with this change by not including more of you in our planning.”