Resource not accessible by integration
See original GitHub issueI try to post a string to create a comment, but getting a Resource not accessible by integration
error
see action logs https://github.com/parsica-php/parsica/pull/37/checks?check_run_id=2113059121
maybe one of the ansi special chars is a problem?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
"Resource not accessible by integration" · Issue #10 - GitHub
I'm confused. This is an action configured in the main repo for a PR in the main repo? All reactions.
Read more >"Resource not accessible by integration" on github post /repos ...
I explicitly assigned allowed all permissions in the workflow but it still doesn't work. Permissions for GH Token are also set to read/write....
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
RequestError [HttpError]: Resource not accessible by integration at /__w/_actions/actions/github-script/v3.1.0/dist/index.js:2137:23 at ...
Read more >Token permissions for GitHub Actions - Damir's Corner
Resource not accessible by integration. Although the message is not entirely clear, I quickly figured out that the problem was insufficient ...
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 Free
Top 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
Yes, it’s not very clear from GitHub’s error message what the problem is. I’ll see if I can catch this particular error and display something more meaningful.
Based on this asnwer, pull_request_target will work after
pull_request_target
event exist in the targeted branch. Thus (example for master branch), first, use:Then merge first to master.
If any fork push to the master branch, the
pull_request_target
will be triggered.