From 72002e8b87b23377716732c08faf952924b86abc Mon Sep 17 00:00:00 2001 From: Kevin Stillhammer Date: Wed, 19 Mar 2025 12:12:56 +0100 Subject: [PATCH] Fix wrong warning message in FAQ (#337) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a7d1b78..1da306e 100644 --- a/README.md +++ b/README.md @@ -448,11 +448,11 @@ because they try to upload with the same cache key. You might see errors like `Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists` -### Why do I see warnings like `Cache not found for keys` +### Why do I see warnings like `No GitHub Actions cache found for key` When a workflow runs for the first time on a branch and has a new cache key, because the [cache-dependency-glob](#cache-dependency-glob) found changed files (changed dependencies), -the cache will not be found and the warning `Cache not found for keys` will be printed. +the cache will not be found and the warning `No GitHub Actions cache found for key` will be printed. While this might be irritating at first, it is expected behaviour and the cache will be created and reused in later workflows.