From 7af89832c5d7f9b5f82862d863b01c749be83331 Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Mon, 8 Jan 2024 13:00:48 -0700 Subject: [PATCH] Further improvements to Merge Queue docs --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 95c2a80..d4a4fd0 100644 --- a/README.md +++ b/README.md @@ -327,8 +327,8 @@ you can configure this by disabling the `cache-read-only` action parameter for t See [Using the cache read-only](#using-the-cache-read-only) for more details. Note there are some cases where writing cache entries is typically unhelpful (these are disabled by default): -- For `pull_request` triggered runs, the cache scope is limited to the merge ref (`refs/pull/.../merge`) and can only be restored by re-runs of the pull request. -- For `merge_queue` triggered runs, the cache scope is limited to a temporary branch with a special prefix created to validate pull request changes. +- For `pull_request` triggered runs, the cache scope is limited to the merge ref (`refs/pull/.../merge`) and can only be restored by re-runs of the same pull request. +- For `merge_group` triggered runs, the cache scope is limited to a temporary branch with a special prefix created to validate pull request changes, and won't be available on subsequent Merge Queue executions. ### Exclude content from Gradle User Home cache