bug: Resource not accessible by integration
See original GitHub issueWhen we use JasonEtco/is-sponsor-label-action
, we get this error:
Run JasonEtco/is-sponsor-label-action@v1
Error: Resource not accessible by integration
✖ fatal GraphqlError: Resource not accessible by integration
at /home/runner/work/_actions/JasonEtco/is-sponsor-label-action/v1/dist/index.js:2463:13
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async makeRequest (/home/runner/work/_actions/JasonEtco/is-sponsor-label-action/v1/dist/index.js:150:20)
at async Toolkit.run.event (/home/runner/work/_actions/JasonEtco/is-sponsor-label-action/v1/dist/index.js:20:21)
https://github.com/remirror/remirror/pull/1210/checks?check_run_id=3511169860
This action works pretty well the whole time and starts to show this error since yesterday.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:10 (1 by maintainers)
Top Results From Across the Web
"Resource not accessible by integration" · Issue #10 - GitHub
This happens as soon as the person creating the PR does not have permission to the repository. I've been all day with this,...
Read more >"Resource not accessible by integration" on github post /repos ...
1 · Hello. · Most of the time, when an operation works with the PAT and not with the GITHUB_TOKEN, it's a scope...
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 >Token permissions for GitHub Actions - Damir's Corner
Recently, the Test Reporter action in one of my workflows failed with the following error message: Resource not accessible by integration.
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
this isn’t a bug for @JasonEtco to fix. It is being caused by a bug that the GitHub team accidently introduced. The team knows about the issue and has prioritized it for fix. I have no clue what that means in terms of when we can expect it to be resolved, but I would assume once they’ve fixed it we’ll start seeing all new PRs and Issues getting the label properly again.
Oh no no no! 😅 It’s just the way the
v1.1.3
tag is at odds with other releases, as the former has itsindex.js
located in adist
subfolder, while others don’t.