From b8cb126311944a8d0566d72e699022e89ac8d833 Mon Sep 17 00:00:00 2001
From: Tara Nelson <6740550+talune@users.noreply.github.com>
Date: Tue, 25 Jun 2024 14:19:59 -0700
Subject: [PATCH] Update instructions for fine grained PAT

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 36ac715..be7cf8c 100644
--- a/README.md
+++ b/README.md
@@ -136,9 +136,9 @@ Using these events ensure that a given issue or pull request, in the workflow's
 
 ## Creating a PAT and adding it to your repository
 
-- create a new [personal access
-  token](https://github.com/settings/tokens/new) with `project` scope. For private repos you will also need `repo` scope. For fine-grained access tokens, you will need to add the organization projects permission, and the repository issues and pull requests permissions.
-  _See [Creating a personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) for more information_
+- Create a new [personal access token](https://github.com/settings/tokens/new). _See [Creating a personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) for more information_
+  - For **Tokens (classic)** include the `project` scope; for private repos you will also need `repo` scope.
+  - For **Fine-grained tokens**, you must first select the appropriate _owner_ and associated _repositories_. Then select _Organization permissions -> `projects` `read & write`_, and _Repository permissions -> `issues` `read-only`_ and _`pull requests` `read-only`_.
 
 - add the newly created PAT as a repository secret, this secret will be referenced by the [github-token input](#github-token)
   _See [Encrypted secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository) for more information_