From 1bd6a2275b5b360f42ab67590ed57a3e390462e0 Mon Sep 17 00:00:00 2001 From: Matt Johnson-Pint Date: Mon, 21 Nov 2022 08:47:17 -0800 Subject: [PATCH] fix typo --- tips-and-workarounds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tips-and-workarounds.md b/tips-and-workarounds.md index 4eb6c5c..7610bfa 100644 --- a/tips-and-workarounds.md +++ b/tips-and-workarounds.md @@ -85,7 +85,7 @@ jobs: #### Re-evaluating the cache key By default, the string resolved from the `key` parameter for restoring the cache will also be used for saving the cache. In some situations it may be preferred to re-evaluate the `key` parameter when saving, such as when part of the key's name is not available until after the restore has completed. In such cases, you can add the option `reevaluate-key: true`. -For example, consider a a .NET solution that doesn't *normally* use `packages.lock.json` lock files. You may still want to generate a lock file for purposes of determining the cache key only. +For example, consider a .NET solution that doesn't *normally* use `packages.lock.json` lock files. You may still want to generate a lock file for purposes of determining the cache key only. ```yaml - name: Cache Packages