-
Notifications
You must be signed in to change notification settings - Fork 212
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
Error: HttpError: Resource not accessible by integration #229
Comments
dorny test-reporter now requires the 'checks' write permission, see dorny/test-reporter#229
dorny test-reporter now requires the 'checks' write permission, see dorny/test-reporter#229 It seems to have been the case for a while, but for some reason missing permissions are now breaking the build. It might be related to the other weird issues we've seen with Dependabot commits recently. PR added the permission to mangrove.js, this commit adds it the rest of the jobs.
dorny test-reporter now requires the 'checks' write permission, see dorny/test-reporter#229 It seems to have been the case for a while, but for some reason missing permissions are now breaking the build. It might be related to the other weird issues we've seen with Dependabot commits recently. PR added the permission to mangrove.js, this commit adds it the rest of the jobs.
I am facing the same issue, looks like the issue is still open. |
@pavelfomin mentions the workaround in their original post, although it could use some more context: If you don't pass the To do this, on a workflow or job that uses this action, add the following YAML at the workflow or job level: permissions:
checks: write More info on that here. Hope this helps. |
This fixed it for me a few days ago |
This looks like a duplicate of #168. |
If anyone have Recommended setup for public repositories configuration, then in the test-report.yml set: permissions:
statuses: write
checks: write
contents: write
pull-requests: write
actions: write |
Permission is needed. ref: dorny/test-reporter#229
Test report failing otherwise. dorny/test-reporter#229
see also #309 |
actually I think this issue was already resolved by #263 |
@djbrown If I had to guess, I would say that a lot of people are probably running into this issue because they have missed that they have to set up two separate workflows as documented in the README.md. There were probably a lot of miscommunications or misunderstandings related to this issue. I am also a bit skeptical about the need of the other permissions which were added to the documentation over time. In my experience, |
Co-authored-by: filipe <[email protected]>
Co-authored-by: filipe <[email protected]>
Please update README to include proper permissions:
The text was updated successfully, but these errors were encountered: