Error "Resource not accessible by integration" is not helpful
See original GitHub issueThe error RequestError [HttpError]: Resource not accessible by integration
is raised when you use incorrect secret (I’ve used secrets.GITHUB_SECRET
instead of a personal access token with repo+workflow permissions). Unfortunately I had no idea I’m doing this wrong and the error message wasn’t pointing out what should be done in this case.
Imho, it would be great to have more obvious error message here.
Full error log: https://github.com/iterative/yolov5/runs/2837021374?check_suite_focus=true
Related discussion: https://github.com/iterative/cml/pull/554#issuecomment-847748393
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
"Resource not accessible by integration" · Issue #10 - GitHub
I've been all day with this, and there does not seem to be a solution. Same problem as here actions/labeler#12. 👍 4
Read more >"Resource not accessible by integration" on github post /repos ...
The problem here is related to the GITHUB_TOKEN permission scope that is generated automatically in a Github Actions workflow run ...
Read more >Resource not accessible by integration - GoReleaser
Integrations that may cause this: Homebrew Tap; Krew Plugins. Fixing it¶. You have basically two options: 1. Use a Personal Access Token (PAT) ......
Read more >GitHub Actions - Resource not accessible by integration
This post will hopefully help anyone searching for the following error. RequestError [HttpError]: Resource not accessible by integration at ...
Read more >GitHub checks: "Resource not accessible by integration"
Hi there, I have a GitHub app, and the GitHub plugin installed. I now have regularly this warning: WARNING ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this can also be caused form permissions on forked repos.
For example commands like
cml send-comment
needwrite
permissions on the repo:I’m not completely sure about the scope of iterative/terraform-provider-iterative#17, but this looks like a different issue. In this case, the error handling logic belongs to CML itself, not the provider.