Clarify reason for including repo scope

This commit is contained in:
Laurence "DC5B" Lord
2023-04-04 15:23:37 +01:00
committed by GitHub
parent 9d30cd4ea3
commit 2eedc0bd12

View File

@@ -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.