From 68b8fbd7818bab307ab1f4abc9a5fa2849912dcc Mon Sep 17 00:00:00 2001 From: Mike Maraya Date: Thu, 22 Dec 2022 10:57:15 -0800 Subject: [PATCH] classic personal access tokens required Clarified that classic personal access tokens, not fine-grained ones, are needed for scorecard to work. Signed-off-by: Mike Maraya --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c7f9b62b848..0e63a41822e 100644 --- a/README.md +++ b/README.md @@ -228,7 +228,7 @@ requests before running Scorecard. There are two ways to authenticate your requests: either create a GitHub personal access token, or create a GitHub App Installation. -- [Create a GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). +- [Create a classic GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-personal-access-token-classic). When creating the personal access token, we suggest you choose the `public_repo` scope. Set the token in an environment variable called `GITHUB_AUTH_TOKEN`, `GITHUB_TOKEN`, `GH_AUTH_TOKEN` or `GH_TOKEN` using the