>_ IzzyLab

Topic breakdown

actions/cache saves a given directory (for example ~/.npm or vendor) between workflow runs under a set key and restores it on the next run on an exact key match — then dependency installation runs much faster. The key is usually built from a hash of the lock file via hashFiles(...): when dependencies change the key changes and the cache is automatically invalidated. A common mistake is to cache a directory but not tie the key to the lock file, so the cache never updates. The step is added to steps via uses: with a with: block (path, key).

What's checked

  1. the workflow passes actionlint
  2. actions/cache is used
  3. the cache key depends on the lock file

What it looks like