## Introduction The `cache-hit` value should be a string boolean, but it seems like not to always be the case ? ## Related runs - twenty-server first attempt saves cache second retrieves it https://github.com/twentyhq/twenty/actions/runs/12768260350 - twenty-front https://github.com/twentyhq/twenty/actions/runs/12767064201
30 lines
958 B
YAML
30 lines
958 B
YAML
name: Restore cache
|
|
inputs:
|
|
key:
|
|
required: true
|
|
description: Prefix to the cache key
|
|
additional-paths:
|
|
required: false
|
|
outputs:
|
|
cache-primary-key:
|
|
description: actions/cache/restore cache-primary-key outputs proxy
|
|
value: ${{ steps.restore-cache.outputs.cache-primary-key }}
|
|
cache-hit:
|
|
description: String bool indicating whether cache has been directly or indirectly hit
|
|
value: ${{ steps.restore-cache.outputs.cache-hit == 'true' || steps.restore-cache.outputs.cache-matched-key != '' }}
|
|
|
|
runs:
|
|
using: composite
|
|
steps:
|
|
- name: Restore cache
|
|
uses: actions/cache/restore@v4
|
|
id: restore-cache
|
|
with:
|
|
key: ${{ inputs.key }}-${{ github.ref_name }}-${{ github.sha }}
|
|
restore-keys: ${{ inputs.key }}-${{ github.ref_name }}-
|
|
path: |
|
|
.cache
|
|
.nx/cache
|
|
node_modules/.cache
|
|
packages/*/node_modules/.cache
|
|
${{ inputs.additional-paths }} |