From 3c1fbef7d3e6be825fd4c4d2dc8fecd28d42df04 Mon Sep 17 00:00:00 2001 From: Maxim Lobanov Date: Tue, 13 Jul 2021 20:35:24 +0300 Subject: [PATCH] Update 0001-support-caching-deps-for-monorepos.md --- docs/adrs/0001-support-caching-deps-for-monorepos.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/adrs/0001-support-caching-deps-for-monorepos.md b/docs/adrs/0001-support-caching-deps-for-monorepos.md index c1478643..923e1896 100644 --- a/docs/adrs/0001-support-caching-deps-for-monorepos.md +++ b/docs/adrs/0001-support-caching-deps-for-monorepos.md @@ -23,8 +23,8 @@ The second option looks more generic because it allows to: ## Decision -Add `deps-lock-file` input that will accept path (relative to repository root) to dependencies lock file. -If provided path contains wildcards, the action will search all maching files and calculate common hash like `${{ hashFiles('**/packages.lock.json') }}` YAML construction does. +Add `package-lock-file` input that will accept path (relative to repository root) to dependencies lock file. +If provided path contains wildcards, the action will search all maching files and calculate common hash like `${{ hashFiles('**/package-lock.json') }}` YAML construction does. The hash of provided matched files will be used as a part of cache key. Yaml examples: @@ -35,7 +35,7 @@ steps: with: node-version: 14 cache: npm - deps-lock-file: 'sub-project/package-lock.json' + package-lock-file: 'sub-project/package-lock.json' ``` ```yml steps: @@ -44,5 +44,5 @@ steps: with: node-version: 14 cache: yarn - deps-lock-file: 'sub-project/**/yarn.lock' + package-lock-file: 'sub-project/**/yarn.lock' ```