Hi. I managed to setup remote caching but I'm still using the github action to install and setup pants. I still see the named caches growing up very fast to 800mb -1gb. Should I nuke it before the end of the pipeline or should I file a bug in the github action to support not saving the named caches?

I think both of those sound sensible: 1. if it's urgent, unblock your CI by either `rm`ing it or just

mv named_caches named_caches_not_cached

(latter is likely faster) 2. contribute a

cache-named-caches

flag to to the

init-pants

action, similar to

cache-lmdb-store

, but with

default: 'true'

. https://github.com/pantsbuild/actions/blob/d767b356a10c6c50fc0db0ddc215611b300b226b/init-pants/action.yaml#L47-L56 (In my work repo, we also use GHA and we don't bother caching the named caches.)

mypy caches inside the named caches are blowing up very fast. I will for sure make a PR there!