Skip to content

Commit bf87972

Browse files
tobyhedeclaude
andcommitted
docs(ci): say why the ImpactGate restore's primary key never matches
Saves always append the run to the commit's key, so no entry is stored under the primary key itself. It remains only to supply cache-primary-key to the REFRESH check and the save key. Co-Authored-By: Claude <noreply@anthropic.com>
1 parent cd9f63b commit bf87972

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

‎.github/workflows/impact.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,8 @@ jobs:
6363
# repository-wide fallback: another release branch has different history.
6464
# Saves append the run to the commit's key (see "Save baselines"), so the
6565
# first restore key finds this commit's newest pair before any ancestor's.
66+
# No entry is ever saved under the primary key itself, so it never matches:
67+
# it is kept only to supply cache-primary-key to REFRESH and the save key.
6668
- name: Restore baselines
6769
id: restore
6870
uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4

0 commit comments

Comments
 (0)