 invalidation is hard to do right, though from a dependency caching perspective it works well once you have figured out what to monitor. Your LLM will not think of this out of the box.

 works well, but... unfortunately I need to figure that out for alpine 

 too. Centralized docker image caching would be good to have too (because right now it only caches on my actions runner instance, which is inefficient for me too, because I'm storing everything 3x)

The real challenge for me has historically been golang, but since 1.25 I should be able to get something going there. Just need to prioritize solving this.

devs

Open source devs consider making hogs pay for every Git pull

0xbitcoiner

This is also because `actions/cache` invalidation is hard to do right, though from a dependency caching perspective it works well once you have figured out what to monitor. Your LLM will not think of this out of the box.

For packages, `apt-cacher-ng` works well, but... unfortunately I need to figure that out for alpine `apk` too. Centralized docker image caching would be good to have too (because right now it only caches on my actions runner instance, which is inefficient for me too, because I'm storing everything 3x)

The real challenge for me has historically been golang, but since 1.25 I should be able to get something going there. Just need to prioritize solving this.