Posting comments (pr-comments) doesn't work for fork repo

[shenxianpeng]

However, I'm still seeing an error in the logs when posting comments. This might be because you’re working from a forked repo (posting comments worked successfully for an unforked PR in #76).

Error posting PR comment: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/issues/comments#create-an-issue-comment", "status": "403"}

Originally posted by @shenxianpeng in #75 (comment)

[StaticRocket]

Actually unsure about this. Not sure why, but I'm seeing the same issue here:

https://github.com/TexasInstruments/processor-sdk-doc/actions/runs/11578282553/job/32231718338

Executing on a non-forked repo.

[shenxianpeng]

This is also fork repo. It is from your repo and merge to upstream repo.

[shenxianpeng]

Before finding a solution for the fork repository, pr-comments option need to be disabled ☹️

[StaticRocket]

Ah, didn't think that counted. I have another workflow that attempts to comment on PRs. Hopefully it will get updated later today and I can see if that also gets hit.

[StaticRocket]

I should have read things a little more.

https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/

[StaticRocket]

Here's what we did for our custom workflow:

https://github.com/TexasInstruments/processor-sdk-doc/blob/master/.github/workflows/rstcheck.yml
https://github.com/TexasInstruments/processor-sdk-doc/blob/master/.github/workflows/comment.yml

So this workflow really just needs a way to save the results as an artifact (or file for use in a later step) instead of pr-comment.