4 ms·
they walked that back for now at least - self-hosted gh runners are still free: https://docs.github.com/en/billing/concepts/product-billing/github-actions https
by exochrono 1mo ago
they walked that back for now at least - self-hosted gh runners are still free: https://docs.github.com/en/billing/concepts/product-billing/github-actions https://docs.github.com/en/billing/concepts/product-billing/...
- inigyou 1mo agoWell, they're still implemented that way.
- arandomhuman 1mo agoCan you share a source for this? it's not that I don't believe you but I've had difficulties finding one.
- js2 1mo agoDo you have a source for this?
- judge2020 1mo agoMore likely is that the log streamer takes up some amount of resources and thus running it requires a baseline level of compute. But I doubt they spin up a small runner per-self-hosted runner, most likely some ruby workers (on distributed azure instances) are dedicated purely to streaming self-hosted runner logs to log consumers. I'm certainly not surprised that they tried to sneak in billing self-hosted runner minutes at some ratio to potentially recoup the costs here. 0: https://docs.github.com/en/enterprise-server@3.21/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server https://docs.github.com/en/enterprise-server@3.21/admin/mana...