I wonder how many of those actions are really necessary

PhilipRoman 6 hours ago | parent | next [-]

And how many of those actions do uncached downloads instead of building self-contained offline images... Speaking of which, I wonder if GitHub has implemented any HTTP interception for common mirror sites, like used by apt, etc.

▲

everfrustrated 5 hours ago | parent | next [-]

GitHub and WarpBuild cache is so slow it is often faster to re-download hundreds of MB each run than cache it properly.

I so wish this wasn't the case.

▲

spockz 6 hours ago | parent | prev [-]

Many downloads now go over https. Intercepting them would require having certificate for those domains. IIRC on the clouds the standard images do have a sources list that points to mirrors on the cloud’s network. I would only presume Github Actions runners have the same.

Not sure if something similar exists for NPM which is big for all things JS.

	▲	munk-a 6 hours ago \| parent [-]
		Other CI/CD platforms usually push you towards using self-hosted mirrors for downloading large chunks of data (often aggressively so) but github is pretty hands off when it comes to actions. It is interesting to consider whether managing that traffic might be overwhelming them and if this can be traced back to a lack of forethought when it came to building out those tools.

▲

bravetraveler 7 hours ago | parent | prev [-]

Or how many pushes those commits are spread across; oh, neat, big number.