Because they host the artifacts, logs, and schedule jobs which run on your runners, I assume.

Then why do they charge by the minute instead of gigabytes and number of events?

	▲	naikrovek 6 days ago \| parent [-]
		Ask them. I don’t set the policy at a company I don’t work at. Their announcement gives a clue, and it’s to do with job orchestration.

▲

falsedan 6 days ago | parent | prev [-]

they charge you for artifacts and logs separately, already

▲

naikrovek 6 days ago | parent [-]

Yep and the sky is blue and GitHub can charge for that too if they want to.

I don’t make policy at GitHub and I don’t work at GitHub so go ask GitHub why they charge for infrastructure costs like any other cloud service. It has to do with the queueing and assignment of jobs which is not free. Why do they charge per minute? I have no idea, maybe it was easiest to do that given the billing infrastructure they already have. Maybe they tried a million different ways and this was the most reasonable. Maybe it’s Microsoft and they’re giving us all the middle finger, who knows.

	▲	falsedan 5 days ago \| parent [-]
		I don't think you're responsible for anything more than your own comments. I added some context that contradicts your assumption that the increased fees were to cover hosting/storage/scheduling costs.