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

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

Open
1 task done
lugi0 opened this issue Mar 17, 2025 · 4 comments
Open
1 task done
Labels
content This issue or pull request belongs to the Docs Content team needs SME This proposal needs review from a subject matter expert waiting for review Issue/PR is waiting for a writer's review

Comments

@lugi0
Copy link

lugi0 commented Mar 17, 2025

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 lugi0 added the content This issue or pull request belongs to the Docs Content team label Mar 17, 2025
Copy link

welcome bot commented Mar 17, 2025

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 17, 2025
@subatoi subatoi added waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Mar 17, 2025
@subatoi
Copy link
Contributor

subatoi commented Mar 17, 2025

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

@subatoi subatoi closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2025
@subatoi subatoi reopened this Mar 18, 2025
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 18, 2025
@subatoi
Copy link
Contributor

subatoi commented Mar 18, 2025

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 subatoi added needs SME This proposal needs review from a subject matter expert and removed triage Do not begin working on this issue until triaged by the team labels Mar 18, 2025
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team needs SME This proposal needs review from a subject matter expert waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

No branches or pull requests

3 participants
@subatoi @lugi0 and others