You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/adrs/0000-caching-dependencies.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ We don't persue the goal to provide wide customization of caching in scope of `a
30
30
- if input contains wildcards (like `**/package-lock.json`), hash of multiple files will be used
31
31
- The hash of file provided in `package-lock-path` input will be used as cache key (the same approach like [actions/cache](https://github.com/actions/cache/blob/main/examples.md#node---npm) recommends)
32
32
- The following key cache will be used `${{ runner.os }}-npm-${{ hashFiles('<package-lock-path>') }}`
33
+
- Action will cache global npm cache directory (retrieved via `npm config get cache`)
33
34
34
35
# Example of real use-cases
35
36
Default use case when `package-lock.json` or `yarn.lock` are located in repository root:
0 commit comments