You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
An error occurs indicating that the fine-grained personal access token does not have access to the required resources for CI-Tests check in private github repository, not encountering error with any other checks besides SAST as well
RESULTS
-------
Writing results to result
Error: check runtime error: CI-Tests: internal error: internal error: Client.Repositories.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Resource not accessible by personal access token
2024/08/21 11:24:41 error during command execution: check runtime error: CI-Tests: internal error: internal error: Client.Repositories.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Resource not accessible by personal access token
Reproduction steps
Steps to reproduce the behavior:
Execute the command scorecard --repo <github repository> --show-details --checks CI-Tests
Expected behavior
scorecard command should complete successfully and generate result without encountering any errors related to access permissions
Additional context
Full read write access to repository permissions for fine-grained PAT still gives error
Other checks run successfully except SAST as well.
Not encountering issue when using classic token
Scorecard Version: 5.0.0
The text was updated successfully, but these errors were encountered:
Describe the bug
An error occurs indicating that the fine-grained personal access token does not have access to the required resources for CI-Tests check in private github repository, not encountering error with any other checks besides SAST as well
Reproduction steps
Steps to reproduce the behavior:
scorecard --repo <github repository> --show-details --checks CI-Tests
Expected behavior
scorecard command should complete successfully and generate result without encountering any errors related to access permissions
Additional context
The text was updated successfully, but these errors were encountered: