Solution for "Error: Resource not accessible by integration"

[zcraber]

This is not a bug report.

Just sharing a solution, that worked for me. In case anyone gets the Error: Resource not accessible by integration while running the workflow, try this:

1. Go to your repository Settings.
2. Select General from Actions.
3. Under Workflow permissions, check Read and write permissions.

Previously, repositories had this setting enabled by default. Seems like this has been changed.

[mre]

Huh, thanks for the heads-up. I wonder why write permissions are required by the action. We don't write anything except for the status report at the end of the run. We don't write anything to the repo itself. Anybody has an idea what's going on? We might need to add further instructions to the readme if this is a common problem.

I will reopen this issue as I'd like to get more feedback.

[zcraber]

Huh, thanks for the heads-up. I wonder why write permissions are required by the action. We don't write anything except for the status report at the end of the run. We don't write anything to the repo itself. Anybody has an idea what's going on? We might need to add further instructions to the readme if this is a common problem.

I will reopen this issue as I'd like to get more feedback.

I guess it's related to https://github.com/peter-evans/create-issue-from-file

[mre]

Do you still encounter this problem? I can't see any issues in any of the other pipelines so far.

[zcraber]

Do you still encounter this problem? I can't see any issues in any of the other pipelines so far.

Nope, it was solved when I enabled Read and write permissions

[mre]

Alright. Thanks for the update. Closing then.

[AndreiCherniaev]

Do you still encounter this problem? I can't see any issues in any of the other pipelines so far.

Nope, it was solved when I enabled Read and write permissions

For me this also helps, great thanks! But how user of lychee-action can know? Is it possible to script before try to create issue script should check settings of the repo and make userfriendly error msg? Or may be we should add such very important note in README.md?
Before start please edit settings of your repo to enable "Read and write permissions"
Screenshort:

@mre @dscho @jacobdalamb

[dscho]

This makes lots of sense, and I agree that:

Error: Resource not accessible by integration

does not clearly say:

Error: This operation is using a token that is missing some scopes;
  You may want to add `issues: write`; For more information, see
  https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#permissions

So: an alternative to default workflow permissions to read/write, and an alternative that I would prefer, personally, would be to add this top-level section to the GitHub workflow definition:

permissions:
  issues: write

Or even better: scope it to the job in the workflow that needs that permission:

jobs:
  my-job:
    permissions:
      issues: write

See a working example that can be imitated.

how user of lychee-action can know?

That's a good point, if you follow the example in the README.md, you wouldn't know. It would probably make for a fine contribution to add that permissions block with a comment along the lines # needed for create-issue-from-file to work here and here. @AndreiCherniaev wanna grab this opportunity to add a notch on your PR belt?

[mre]

@AndreiCherniaev, are you interested in sending a pull request?