From 46572c6bc7c6298c43d06f9c44ff7837ef6daade Mon Sep 17 00:00:00 2001 From: Sankalp Kotewar <98868223+kotewar@users.noreply.github.com> Date: Wed, 11 Jan 2023 10:06:07 +0530 Subject: [PATCH] Update CACHING.md Co-authored-by: Bishal Prasad --- CACHING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CACHING.md b/CACHING.md index 23f5094..b1a909c 100644 --- a/CACHING.md +++ b/CACHING.md @@ -21,7 +21,7 @@ In your workflows, you can use different strategies to name your key depending o ### Updating cache for any change in the dependencies -One of the most common use case is to use hash for lockfile as key. This way same cache will be restored for same lockfiles until there's any change in the lockfile/dependencies. +One of the most common use case is to use hash for lockfile as key. This way, same cache will be restored for a lockfile until there's a change in dependencies listed in lockfile. ```yaml - uses: actions/cache@v3