Copilot quota for a robot / CI account to assign reviews
- Dominant language
- Go
- Stars
- 298
- Forks
- 863
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 36
Description
we had a discussion that we could utilize the k8s-ci-robot or another robot as a holder of CNCF provided Copilot token quota and then opt-in repositories could have support for `/cc copilot` where someone (OWNER file members?) could request or re-request review from Copilot to help out.
there are various ongoing slack threads and issues on the AI review topics and eventually we should probably enable something. currently even CNCF maintainers who have GitHub Enterprise don't have "maintainer" access in certain repos and can't request Copilot review because they don't see the cog wheel.
what people likely do today is download a .patch locally and review it "offline".
https://kubernetes.slack.com/archives/C01672LSZL0/p1778659617475429
https://kubernetes.slack.com/archives/C01672LSZL0/p1778697221619319
[#5930](https://github.com/kubernetes/org/issues/5930) (coderabbit for jobset and kueue) - Since Oct 2025
[#6296](https://github.com/kubernetes/org/issues/6296) (AI review tool for agent-sandbox) - Since Apr 2026
[#6363](https://github.com/kubernetes/org/issues/6363) (coderabbit for mcp-lifecycle-operator) - Just opened
Contributor guide
Research direction
Start by reading the related issues #5930, #6296, and #6363, then review the two linked Slack threads for the existing AI-review discussion. Clarify how k8s-ci-robot or another robot, repository opt-in, OWNER-file permissions, and `/cc copilot` would fit together. Done should mean an agreed, implementable workflow for requesting or re-requesting Copilot reviews.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100