From 30fd9f94bcc75ff514e7bd26fd3c6f5b3ab70aa9 Mon Sep 17 00:00:00 2001
From: Geoff <geoff@gapple.ca>
Date: Wed, 23 Mar 2022 00:14:36 -0700
Subject: [PATCH] Update README.md (#206)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index d6a99d4..140d2b7 100644
--- a/README.md
+++ b/README.md
@@ -177,7 +177,7 @@ Do this to avoid checking out the repository in a detached state.
 ### Commits made by this Action do not trigger new Workflow runs
 
 The resulting commit **will not trigger** another GitHub Actions Workflow run.
-This is due to [limitations set by GitHub](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#triggering-a-workflow-from-a-workflow).
+This is due to [limitations set by GitHub](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow).
 
 > When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.