The PAT scope "read:repo" vs "public_repo"

[lukech]

In the "Actions" section of the readme, "read:repo" is listed as one scope that needs to be selected when creating a personal access token (PAT). When attempting to create a PAT (the classic) I found that "read:repo" was not an option ("read:repo_hook" is the closest one that I ticked). With this PAT/secret my Github actions run (the "build" job) failed with the below signature, indicating the "public_repo" scope is required.

GraphqlResponseError: Request failed due to following response errors:
 - Your token has not been granted the required scopes to execute this query. The 'totalCount' field requires one of the following scopes: ['public_repo'], but your token has only been granted the: ['read:org', 'read:project', 'read:repo_hook'] scopes. Please modify your token's scopes at: https://github.com/settings/tokens.

After recreating a new PAT with the "public_repo" scope (besides "read:org" and "read:project") the build step passed.

Could someone please confirm that the non-existent "read:repo" PAT scope should be replaced by the "public_repo" scope in the readme? Thanks.

[bmuenzenmeyer]

Could someone please confirm that the non-existent "read:repo" PAT scope should be replaced by the "public_repo" scope in the readme? Thanks.

Not with the GH OSPO, but my company's, and I can confirm that public_repo worked for me today

[lukech]

Thanks for confirming @bmuenzenmeyer. I hope one of the maintainers could advise if the readme needs an update by including the "public_repo" scope (and possibly removing the "read:repo" scope).

[ChrisCarini]

Also confirmed. Gave an approval to #168 (review) - hopefully one of the maintainers of this repo takes a look and accepts the PR.