From 9d30cd4ea34b6e5553ef6097e4953de95d9f55d2 Mon Sep 17 00:00:00 2001 From: "Laurence \"DC5B\" Lord" Date: Tue, 4 Apr 2023 14:23:05 +0100 Subject: [PATCH 1/3] Add details about using a classic PAT Let's include details in the readme to avoid error because of the following: > Personal access tokens with fine grained access do not support the GraphQL API. > 'projectV2' field requires the scopes 'read:project' > 'addProjectV2ItemById' field requires the scope 'project' --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 14a0f195..41072e4e 100644 --- a/README.md +++ b/README.md @@ -137,9 +137,11 @@ 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 `repo` and `project` scopes + token](https://github.com/settings/tokens/new) with `project` scopes. _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_ + > **NOTE:** ℹ️ Use a classic token with full control of projects. Personal access tokens with fine grained access do not support the GraphQL API. Only 'project' and 'read:project' scopes are required. + - 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_ From 2eedc0bd12dbc9a780f552802d18e45fdf459731 Mon Sep 17 00:00:00 2001 From: "Laurence \"DC5B\" Lord" Date: Tue, 4 Apr 2023 15:23:37 +0100 Subject: [PATCH 2/3] Clarify reason for including repo scope --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 41072e4e..f1e2c1bc 100644 --- a/README.md +++ b/README.md @@ -137,7 +137,7 @@ 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` scopes. + token](https://github.com/settings/tokens/new) with `project` scope. For private repos you will also need `repo` scope. _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_ > **NOTE:** ℹ️ Use a classic token with full control of projects. Personal access tokens with fine grained access do not support the GraphQL API. Only 'project' and 'read:project' scopes are required. From 539b3f97fd7052344b30e55135ff8a3bc2d8a714 Mon Sep 17 00:00:00 2001 From: "Laurence \"DC5B\" Lord" Date: Tue, 4 Apr 2023 15:24:31 +0100 Subject: [PATCH 3/3] Remove duplicate information about scopes --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f1e2c1bc..f05514fb 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ Using these events ensure that a given issue or pull request, in the workflow's token](https://github.com/settings/tokens/new) with `project` scope. For private repos you will also need `repo` scope. _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_ - > **NOTE:** ℹ️ Use a classic token with full control of projects. Personal access tokens with fine grained access do not support the GraphQL API. Only 'project' and 'read:project' scopes are required. + > **NOTE:** ℹ️ Use a classic token with full control of projects. Personal access tokens with fine grained access do not support the GraphQL API. - 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_