docs icon indicating copy to clipboard operation
docs copied to clipboard

adding reactions to a "pull request review comment" does not work with listed token

Open lugi0 opened this issue 8 months ago • 7 comments

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/rest/reactions/reactions?apiVersion=2022-11-28#create-reaction-for-a-pull-request-review-comment

What part(s) of the article would you like to see updated?

https://docs.github.com/en/rest/reactions/reactions?apiVersion=2022-11-28#create-reaction-for-a-pull-request-review-comment--fine-grained-access-tokens

Additional information

I have been trying to leave a reaction to a PR review comment, following the documentation available here: https://docs.github.com/en/rest/reactions/reactions?apiVersion=2022-11-28#create-reaction-for-a-pull-request-review-comment

I've tried to create PATs for multiple accounts, and even tried to use a PAT of the same user who left the review on a PR in a repo owned by that user, but with every one of those I've always received the response

Insufficient scopes for reacting to this Pull Request Review Comment. (HTTP 403)

I've tried doing this with both curl and the gh api CLI.

I don't know if the documentation is wrong/outdated or if I'm doing something wrong myself, but I believe I've created a fine-grained PAT with write access on the repository as asked

lugi0 avatar Mar 17 '25 15:03 lugi0

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

welcome[bot] avatar Mar 17 '25 15:03 welcome[bot]

Hi @lugi0, thanks for reporting this—we'll review this as soon as we can

subatoi avatar Mar 17 '25 17:03 subatoi

Apologies, I previously closed this by mistake but I actually can reproduce it. I'm afraid I can't guarantee a timeframe for a response as we're not GitHub Support, but thank you for reporting it; I'll investigate it internally.

subatoi avatar Mar 18 '25 13:03 subatoi

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert :eyes:

github-actions[bot] avatar Mar 18 '25 13:03 github-actions[bot]

This is a gentle bump for the docs team that this issue is waiting for technical review.

github-actions[bot] avatar Apr 16 '25 16:04 github-actions[bot]

This is a gentle bump for the docs team that this issue is waiting for technical review.

github-actions[bot] avatar May 15 '25 16:05 github-actions[bot]

This is a gentle bump for the docs team that this issue is waiting for technical review.

github-actions[bot] avatar Jun 13 '25 16:06 github-actions[bot]

I think I encountered the same issue of lack of documentation for required scopes — in my case I tried to use the endpoint Create reaction for a release, which describes the scope requirements as:

The fine-grained token does not require any permissions.

However, attempted usage only results in 4xx responses without granting the scope public_repo.

jsejcksn avatar Aug 02 '25 17:08 jsejcksn

This is a gentle reminder for the docs team that this issue is waiting for technical review by a subject matter expert (SME).

github-actions[bot] avatar Sep 03 '25 16:09 github-actions[bot]