Skip to content

Commit

Permalink
classic personal access tokens required (ossf#2565)
Browse files Browse the repository at this point in the history
Clarified that classic personal access tokens, not fine-grained ones, are needed for scorecard to work.

Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com>

Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com>
  • Loading branch information
mmaraya authored and raghavkaul committed Mar 6, 2023
1 parent 8365f04 commit a767e7f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -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
Expand Down

0 comments on commit a767e7f

Please sign in to comment.