PAT v2 with read+write PR perms not able to read pull request reviewers via GraphQL? #139651
Replies: 2 comments 1 reply
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Hi @dead-claudia! If possible, can you try opening a ticket on our Support page? Support may need to dig in and take a look here. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Weirdly failing action: https://github.com/MithrilJS/mithril.js/actions/runs/11025298266/job/30620204900
Workflow: https://github.com/MithrilJS/mithril.js/blob/d033c66405c766f3e36ea34cb63129666dde766d/.github/workflows/issue-create.yml
Called workflow: https://github.com/MithrilJS/infra/blob/a2f9237c171b78d08a9c962d840deed626a34f68/.github/workflows/notify-triage.yml
Token:

Error:

I'm beyond lost here, because it should have permission. At the very least, the secret is clearly being passed, as it's censored and not just empty.
Checking the GitHub API docs, the relevant info for pull requests is explicitly granted, and GraphQL should support v2 personal access tokens, so nothing suggests to me that it shouldn't be supported.
Beta Was this translation helpful? Give feedback.
All reactions