Skip to content
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

"Resource not accessible by integration" error #176

Closed
StilesCrisis opened this issue Aug 31, 2023 · 5 comments · Fixed by #189
Closed

"Resource not accessible by integration" error #176

StilesCrisis opened this issue Aug 31, 2023 · 5 comments · Fixed by #189

Comments

@StilesCrisis
Copy link

I'm new to Github Actions so this might be a simple issue, but I wasn't able to sort it out.
I tried installing the /remind plugin to my repo and it is giving an error "Resource not accessible by integration".
What does this mean?
Thanks.

Run agrc/create-reminder-action@v1
  with:
    .....
  HttpError: Resource not accessible by integration
      at /home/runner/work/_actions/agrc/create-reminder-action/v1/webpack:/create-reminder-action/node_modules/@octokit/request/dist-node/index.js:86:1
      at processTicksAndRejections (node:internal/process/task_queues:96:[5](https://github.com/Ultrasquid9/this-is-a-terrible-idea/actions/runs/6037004425/job/16380424783#step:2:5))
      at run (/home/runner/work/_actions/agrc/create-reminder-action/v1/webpack:/create-reminder-action/index.js:[7](https://github.com/Ultrasquid9/this-is-a-terrible-idea/actions/runs/6037004425/job/16380424783#step:2:8)1:1)
@StilesCrisis
Copy link
Author

StilesCrisis commented Aug 31, 2023

I figured it out. The provided workflow yaml is missing any permissions. (from https://github.com/agrc/create-reminder-action#sample-usage )

https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/#setting-permissions-in-the-workflow

You need to include a permissions: block.

@stdavis
Copy link
Member

stdavis commented Aug 31, 2023

Interesting. We haven't had to set any permissions for this workflow. Perhaps because we have different org-level setting than you do? This is what ours is set to:
image

What permission(s) did you have to add to get it working? issues: write?

@StilesCrisis
Copy link
Author

I didn't attempt to narrow it down in the least. This repo holds nothing secret. I just turned on anything that sounded remotely relevant.

permissions:
  actions: write
  checks: write
  contents: write
  issues: write
  pull-requests: write
  statuses: write

@steveoh
Copy link
Member

steveoh commented Aug 31, 2023

We can add the tool that checks what is required for a run or two and update the docs. These are related to new GitHub security features.

steveoh added a commit that referenced this issue Oct 4, 2023
@steveoh
Copy link
Member

steveoh commented Oct 4, 2023

/remind me to look at the action run to see the required permissions tomorrow

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 a pull request may close this issue.

3 participants