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

Error: HttpError: Resource not accessible by integration #229

Open
pavelfomin opened this issue Feb 9, 2023 · 8 comments
Open

Error: HttpError: Resource not accessible by integration #229

pavelfomin opened this issue Feb 9, 2023 · 8 comments

Comments

@pavelfomin
Copy link

Please update README to include proper permissions:

    permissions:
      checks: write
espendk added a commit to mangrovedao/mangrove.js that referenced this issue Mar 26, 2023
dorny test-reporter now requires the 'checks' write permission, see dorny/test-reporter#229
espendk added a commit to mangrovedao/mangrove.js that referenced this issue Mar 27, 2023
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.
espendk added a commit to mangrovedao/mangrove.js that referenced this issue Mar 27, 2023
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.
@aquadirjha
Copy link

I am facing the same issue, looks like the issue is still open.
Did anyone find a workaround?

@samkearney
Copy link

Did anyone find a workaround?

@pavelfomin mentions the workaround in their original post, although it could use some more context:

If you don't pass the token argument to this action, it uses GITHUB_TOKEN by default. You can read about how permissions are assigned to GITHUB_TOKEN here. If your repository does not grant permissive defaults to GITHUB_TOKEN, then you need to add the checks: write permission so that the test reporter can write to the 'checks' API to publish the test report.

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.

@AlexZeitler
Copy link

This fixed it for me a few days ago

YannCebron added a commit to JetBrains/gradle-changelog-plugin that referenced this issue Apr 24, 2023
YannCebron added a commit to JetBrains/gradle-changelog-plugin that referenced this issue Apr 24, 2023
@JojOatXGME
Copy link
Contributor

This looks like a duplicate of #168.

@DariuszPorowski
Copy link

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

@djbrown
Copy link

djbrown commented Apr 18, 2024

see also #309

@djbrown
Copy link

djbrown commented Apr 18, 2024

actually I think this issue was already resolved by #263

djbrown added a commit to djbrown/gnucash-android that referenced this issue Apr 18, 2024
@JojOatXGME
Copy link
Contributor

@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, checks: write is the only permission you have to specify, assuming you correctly split the CI into two workflows.

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

No branches or pull requests

7 participants