Skip to content

Explain required GITHUB_TOKEN permissions #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 16, 2022

Conversation

chadxzs
Copy link
Contributor

@chadxzs chadxzs commented Jul 15, 2022

By default the GITHUB_TOKEN is given the required permissions to make
the API requests made by this action. If you set explicit permissions on
your token, however, the default permissions do not apply.

If you run the action without the appropriate permissions, you will see
an error message saying: "Error: Resource not accessible by integration"

This patch updates the README to explain that, if you are using explicit
permissions, you must specify the actions:read permission for the
action to work correctly.

By default the `GITHUB_TOKEN` is given the required permissions to make
the API requests made by this action. If you set explicit permissions on
your token, however, the default permissions do not apply.

If you run the action without the appropriate permissions, you will see
an error message saying: "Error: Resource not accessible by integration"

This patch updates the README to explain that, if you are using explicit
permissions, you must specify the `actions:read` permission for the
action to work correctly.
@softprops softprops merged commit 1711cd2 into softprops:master Jul 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants