Closed zcraber closed 1 year ago
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.
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
Do you still encounter this problem? I can't see any issues in any of the other pipelines so far.
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
Alright. Thanks for the update. Closing then.
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:Settings
.General
fromActions
.Workflow permissions
, checkRead and write permissions
.Previously, repositories had this setting enabled by default. Seems like this has been changed.