-
Notifications
You must be signed in to change notification settings - Fork 37
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
fetch.py: Resource not accessible by integration / 403 HTTP response #58
Comments
It looks like even a full-scoped GITHUB_TOKEN isn't enough:
Seems like a personal access token is required now, injected via secrets. |
that is, the docs need to be overhauled. |
also, the |
Taken care of, I think. |
Hi @jgehrcke - I have followed your tutorial and setup the personal token permissions as stated above, but I still have the Error: Resource not accessible by integration error message. How can I further debug this? |
@gtabboud you could try doing
with your authentication token -- this would for starters provide an unambiguous signal for whether or not the token you want to use really has the right privileges associated. |
When I started this project the
GITHUB_TOKEN
injected into a job was able to read repo traffic API endpoints.However, that does not work anymore, probably for all repositories. I think this since this change: https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/
Log example:
The text was updated successfully, but these errors were encountered: