From 5135979b9e4d7c5cbdebdd9be27e31ee407e3d0b Mon Sep 17 00:00:00 2001
From: Steven Ryland <stevenry@outlook.com>
Date: Thu, 17 Jul 2025 12:50:51 -0700
Subject: [PATCH] Update manage-caches.md to use ${{ github.token }} in the
 example

This is better than implying/asking the user to create a secret called GITHUB_TOKEN, which is kinda the legacy way of giving Actions the ability to call back to Github APIs.
---
 .../managing-workflow-runs/manage-caches.md                     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches.md b/content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches.md
index 62b0f34792b2..3ed5475423dc 100644
--- a/content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches.md
+++ b/content/actions/how-tos/managing-workflow-runs-and-deployments/managing-workflow-runs/manage-caches.md
@@ -76,7 +76,7 @@ jobs:
           done
           echo "Done"
         env:
-          GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          GH_TOKEN: {% raw %}${{ github.token }}{% endraw %}
           GH_REPO: {% raw %}${{ github.repository }}{% endraw %}
           BRANCH: refs/pull/{% raw %}${{ github.event.pull_request.number }}{% endraw %}/merge
 ```