Allow GitHub Apps to be assigned as pull request reviewers #193037
Replies: 4 comments
|
💬 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. ⭐ |
|
Is there an update on this request please? |
|
I would also like this feature. I'd also like the ability to enable dropdown options similar to the Copilot review bots reasoning mode. |
|
I’d also find the reasoning-mode option useful. In an AI review workflow, being able to choose how deeply the agent analyzes a PR could help balance review quality, latency, and cost depending on the PR size or risk level. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
Third-party GitHub Apps can't be added to the reviewers array on a pull request, attempting it via
gh pr edit --add-reviewerreturns:GraphQL: Could not resolve user with login 'APP_NAME[bot]'. (requestReviewsByLogin)My use case is to have custom AI code review agents deployed as GitHub Apps inside private orgs. These tools do sophisticated review workflows but can't participate in the native reviewer UX, they can only post unsolicited comments.
This could also apply to tools like Codex or Claude Code trying to work as Copilot-style reviewers.
What I'd want: an installed GitHub App shows up in the Reviewers sidebar in a pending state, assigned through the same UI and API that humans use, resolving when the app submits a review.
GitHub already does this for Copilot, I would like to be able to build on the same foundation.
Gating it on
pull_requests: writeplus an explicit repo/org-level opt-in seems like a reasonable way to control surface area.Adjacent discussions I found, but not quite the same: #157751, #186152.
All reactions