From ef11f54eee2bfc69a7adcf6cd1b0423068dce940 Mon Sep 17 00:00:00 2001
From: Michael Vorburger <vorburger@google.com>
Date: Sat, 11 Mar 2023 19:40:53 +0100
Subject: [PATCH] Fix example for Bazel

---
 examples.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/examples.md b/examples.md
index 7319a10..4136623 100644
--- a/examples.md
+++ b/examples.md
@@ -661,14 +661,18 @@ steps:
 
 ## * - Bazel
 
-Bazel cache has a good handle to check if cached content should be rebuild or not based on its inputs like a hash(command + files). So using the latest cache of the branch is enough, no need to suffix with `hashFiles('**/...')`.
-
 ```yaml
 - name: Cache Bazel
-  uses: actions/cache@v2
+  uses: actions/cache@v3
   with:
     path: |
-      ~/.cache/bazelisk
-      ~/.cache/bazel
-    key: ${{ runner.os }}-bazel
+      ~/.cache/bazel # Linux
+      /private/var/tmp/_bazel_runner/ # macOS
+      # TODO Add Windows if you know where it is, based on https://bazel.build/remote/output-directories
+    key: ${{ runner.os }}-bazel-${{ hashFiles('.bazelversion', '.bazelrc', 'WORKSPACE', 'WORKSPACE.bazel', 'MODULE.bazel') }}
+    restore-keys: |
+      ${{ runner.os }}-bazel-
+- run: bazelisk test //...
 ```
+
+[`bazelisk`](https://github.com/bazelbuild/bazelisk) does not have be to separately downloaded and installed because it's already included in GitHub's `ubuntu-latest` base image.