From f9a2fcb99f62be7b026929f88f7a28593954b5af Mon Sep 17 00:00:00 2001
From: Peter Evans <18365890+peter-evans@users.noreply.github.com>
Date: Mon, 25 Nov 2024 01:02:09 -0800
Subject: [PATCH] clarify when workflow scope is necessary

---
 docs/concepts-guidelines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/concepts-guidelines.md b/docs/concepts-guidelines.md
index 555f475..715492a 100644
--- a/docs/concepts-guidelines.md
+++ b/docs/concepts-guidelines.md
@@ -231,7 +231,7 @@ It will use their own fork to push code and create the pull request.
 
 1. Create a new GitHub user and login.
 2. Fork the repository that you will be creating pull requests in.
-3. Create a Classic [Personal Access Token (PAT)](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with `repo` [and `workflow`](https://github.com/peter-evans/create-pull-request/issues/3510) scopes.
+3. Create a Classic [Personal Access Token (PAT)](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) with `repo` scope. If the upstream repository uses GitHub Actions, it's highly likely that you will also need the `workflow` scope.
 4. Logout and log back into your main user account.
 5. Add a secret to your repository containing the above PAT.
 6. As shown in the following example workflow, set the `push-to-fork` input to the full repository name of the fork.