- name: List caches run: | curl -H "Authorization: token $ secrets.GITHUB_TOKEN " \ -H "Accept: application/vnd.github+json" \ https://api.github.com/repos/$ github.repository /actions/caches
Debugging the action cache feels like detective work. By using debug-action-cache methodologies to peel back the layers of digests and fingerprints, you move from "guessing why the build is slow" to "knowing exactly why it’s re-running." debug-action-cache
If using actions/cache@v3 , add the verbose input: - name: List caches run: | curl -H
Combine this with debug logs showing the restore key that was used. If you see Linux-pip-staging , you know the problem is branch isolation. and command-line flags between two builds.
: By using the debug tools, you can dump the ActionKey and compare the list of inputs, environment variables, and command-line flags between two builds.