find-comment@v3 fails with "not found" when running on a pull request

[jason-curtis]

find-comment@v3 fails with "not found" when running on a pull request

[jason-curtis]

Ah, I see. Thank you for the response! I forgot that GH likes to return 404s instead of 401s, and I was confused because I had earlier had an explicit permissions error (something like this token does not have access to this resource).

In any case, I worked around it by using the GITHUB_TOKEN directly and setting up permissions within the action:

    permissions:
      contents: read
      pull-requests: write

I also ended up using @mshick/add-pr-comment since it was a bit more straightforward for my use case.

[peter-evans]

Hi @jason-curtis

In the backend of GitHub, pull requests are extended issues. They use the same API. So the action is correct to try and find an issue with that number.

If you are consistently getting a 404 from the API then that would probably indicate that the token you are using doesn't have the correct permissions to access the repository contents.

• Check the COMMENTING_ACCESS_TOKEN secret actually contains the full PAT and hasn't been accidentally truncated. Copy/paste it again.
• Check that the PAT is created on a user that has read and write access to the target repository.
• Check that the PAT has the correct scopes. repo for classic tokens.