From 35e7172b89d803308dcfde981c7765995eb6d25b Mon Sep 17 00:00:00 2001 From: Mark Hildreth <113933455+markhildreth-gravity@users.noreply.github.com> Date: Mon, 7 Nov 2022 11:02:10 -0500 Subject: [PATCH] Correct documentation on gha scopes I believe the documentation is misleading in saying that specifying a scope in a gha cache declaration will `ensure each branch gets its own cache`. I believe this should say that each build or each image will get its own cache. Signed-off-by: Mark Hildreth --- docs/manuals/cache/backends/gha.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manuals/cache/backends/gha.md b/docs/manuals/cache/backends/gha.md index b34b5a32..f3eedfb2 100644 --- a/docs/manuals/cache/backends/gha.md +++ b/docs/manuals/cache/backends/gha.md @@ -64,7 +64,7 @@ leaving only the final cache. To preserve the cache for multiple builds on the same branch, you can manually specify a cache scope name using the `scope` parameter. In the following example, the cache is set to a combination of the branch name and the image -name, to ensure each branch gets its own cache): +name, to ensure each image gets its own cache): ```console $ docker buildx build --push -t / \