From e999d08944143881c4c490e70d275016d7c626c3 Mon Sep 17 00:00:00 2001 From: Sankalp Kotewar <98868223+kotewar@users.noreply.github.com> Date: Wed, 11 Jan 2023 10:11:56 +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 09e936a..ec54282 100644 --- a/CACHING.md +++ b/CACHING.md @@ -211,7 +211,7 @@ If you want to avoid re-computing the cache key again in `save` action, the outp ### Re-evaluate cache key while saving cache -With save action, the key can now be re-evaluated while executing the action. This helps in cases where the lockfiles are generated during the build. +On the other hand, the key can also be explicitly re-computed while executing the save action. This helps in cases where the lockfiles are generated during the build. Let's say we have a restore step that computes key at runtime