Allow updating an existing cache

[davidsbond]

GitHub actions supports caching across builds which is super powerful. However, once a cache has been saved it can no longer be modified. While this is fine for most scenarios where you need the cache there are a few times when you would like to update it.

I created this PR on the actual cache action to allow updating a cache when providing it in configuration:

actions/cache#353

I created it after reading the related issue:

actions/cache#342

However, it seems like something either needs to change in this package or server-side on the actions cache.

My use-case for wanting to update a cache is when using GitHub actions in golang projects. Go supports a test cache which allows tests to be skipped if the code they use has not changed, which can significantly improve test times (especially in large projects). Each time I run my tests, I'd like to maintain a single cache for tests, that way, when a run completes I can update the cache and all my workflows share a single test cache

There are some extra use-cases described on the issue above.

[smorimoto]

I would also like to support this proposal.

[half2me]

I need this too

[eLarocque]

same

[CAMOBAP]

[Blissful89]

#poke

[hyperxpro]

+1

[stephanrotolante]

+1

[DenizUgur]

+1

[emrebayramc]

+1

[YegorMedvedev]

In the meantime, here's a workaround that I use:

- name: Get cache
  uses: actions/cache@v3
  with:
    path: ... # a list of cache paths
    key: ${{ runner.os }}-my-cache-${{ github.head_ref }}-${{ hashFiles(...for example yarn.lock...) }}

- name: Do something to change a cache
  run: ...

- name: Enforce cache update for a local NX cache
  run: |
    STATE_CACHE_KEY="${{ runner.os }}-my-cache-${{ github.head_ref }}-${{ hashFiles(...) }}"
    echo "STATE_CACHE_KEY=${STATE_CACHE_KEY}" >> $GITHUB_ENV

[emrebayramc]

+1

[wind57]

+1

[arpanrec]

+1

[bexsoft]

+1

[nnsay]

+1

[dsame]

Updating the cache is supposed to be done with restore-keys

This input allows to restore the cache even if it is not fully matched. And to generate the new key to update the cache do one of:

1. include the changing file into ${{ hashFiles(...) }}
2. set output of the previous step and include it into the key

[isaacbowen]

@dsame This is exactly what I was missing. Thank you for sharing! Super super super helpful. ❤️

[pauldraper]

@dsame's workaround is the best available currently, though it does have problems.

Github hard-limits repos to 10GB of caches. So creating lots of caches can push other less-frequent-but-helpful caches to deletion. Whereas if you could update/replace an existing cache, that wouldn't happen.

[lcswillems]

On Gitlab or a lot of other different CI/CD tools, this is built-in 😭 Such a pain not to have this!