Debug-action-cache

GitHub doesn’t let you browse caches directly, but you can list them via API:

- name: Validate cache integrity run: | if [ -f node_modules/.cache_hash ]; then STORED_HASH=$(cat node_modules/.cache_hash) CURRENT_HASH=$(sha256sum package-lock.json | cut -d' ' -f1) if [ "$STORED_HASH" != "$CURRENT_HASH" ]; then echo "::warning::Cache hash mismatch! Forcing cache invalidation." rm -rf node_modules fi fi debug-action-cache

Use flags like --execution_log_json_file (in Bazel) to dump exactly what was sent to the cache. GitHub doesn’t let you browse caches directly, but

However, the fundamentals remain: You cannot optimize what you cannot measure. Until GitHub provides a full Cache UI with version history, manual debugging using ACTIONS_STEP_DEBUG remains the most powerful tool in your DevOps arsenal. debug-action-cache

Caching not working · community · Discussion #163260 - GitHub