"Resource not accessible by integration" on forks

[vakker]

Hi,
If the action is run from a fork then it raises Resource not accessible by integration.
It seems to be related to this issue.

Maybe with the set-output feature (see here) the files could be directly piped to the comment step instead of writing to a file.

[MishaKav]

Can you be more specific? Or maybe you can share an example of what are you trying to do?

[vakker]

So for example this test run shows the issue.

[MishaKav]

As I can see from your log, it successfully generated all data, but when it tries to put a comment it gets status: 403 - it's meaning your GITHUB_TOKEN didn't have permission to create comments. You can read more in Automatic token authentication.
What you can do is create the right token and pass it to params

- name: Pytest coverage comment
   uses: MishaKav/pytest-coverage-comment@main
   with:
     token: {{ secrets.GITHUB_TOKEN }}
     pytest-coverage-path: ./pytest-coverage.txt
     junitxml-path: ./pytest.xml
     hide-report: true

or specify the permissions for default GITHUB_TOKEN in your workflow:

on:
  push:
    branches: [ master ]
permissions: read-all|write-all

[vakker]

Thanks for the answer, but I'm not sure that's really the issue. Please take a look on this discussion that elaborates the issue more that I linked earlier.

[MishaKav]

That is the issue, when you run your workflow, the GITHUB_TOKEN that you provided didn't have permission to post a comment, because it didn't have the permission to write issue. Attach the screenshot from your workflow.

[MishaKav]

you also can try this solution #68 (comment)