You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maka.apache.org by Lei Yuhan <le...@outlook.com> on 2026/08/20 11:43:46 UTC
[DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Hi all,
CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
* CodeRabbit: https://github.com/apps/coderabbitai
* Qodo Code Review: https://github.com/apps/qodo-code-review
Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
Thanks,
Yuhan
AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
RE: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Lei Yuhan <le...@outlook.com>.
Thanks, Yongtao. I checked this.
I could not find public evidence of another Apache repository using CodeRabbit
or Qodo. GitHub's commenter search found activity from those bots only under
apache/maka, and that appears to be history from before the transfer. We should
not treat it as an ASF precedent.
ASF does support AI review bots in general. The official .asf.yaml tooling has
a copilot_code_review setting, and projects including Arrow and Thrift
currently enable it:
https://github.com/apache/infrastructure-asfyaml
https://github.com/apache/arrow/blob/main/.asf.yaml
https://github.com/apache/thrift/blob/master/.asf.yaml
I found no blanket ASF policy approving CodeRabbit or Qodo. Infra's published
process says requests to add or configure a third-party service should go
through an INFRA ticket backed by the project's public agreement:
https://infra.apache.org/jira-guidelines.html
I propose narrowing the next step accordingly. After this discussion, the two
INFRA tickets would ask Infra to review each app's permissions and install it
only if acceptable. Project consensus would authorize making the requests, not
approve the apps on Infra's behalf.
I will keep the thread open for the stated period. If no unresolved objections
remain, I will include this thread and the permission details in the tickets.
Thanks,
Yuhan Lei
(astrohan, @Astro-Han on GitHub)
AI use: Codex helped check the public evidence and draft this reply. I verified
the searches and conclusions.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
Re: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Yongtao Wang <wy...@apache.org>.
I agree that review bots can take quite a bit of pressure off maintainers, and for Maka I think they can be genuinely useful given the amount of review work we have.
My main concern is more about the ASF side of this. I'm not sure what the current ASF/Infra position is on third-party review bots, especially considering the permissions these GitHub Apps require and the fact that repository/PR data may be processed by an external service.
I'm also wondering whether other projects under the Apache GitHub organization are already using CodeRabbit, Qodo, or similar review bots. I haven't looked into this myself, so I don't know whether there is already some precedent here. If there is, it would be useful to understand how the permissions and third-party access were handled in those cases.
So I don't have an objection to the idea itself, but I think it would be good to clarify the ASF/Infra expectations around these permissions before we proceed.
On 2026/08/20 11:43:46 Lei Yuhan wrote:
> Hi all,
>
> CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
>
> I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
>
> * CodeRabbit: https://github.com/apps/coderabbitai
> * Qodo Code Review: https://github.com/apps/qodo-code-review
>
> Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
>
> The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
>
> If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
>
> Thanks,
> Yuhan
>
> AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
回复: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by 常 宇航 <ch...@outlook.com>.
+1 from me, I support filing separate INFRA tickets for CodeRabbit and Qodo, limited to apache/maka, advisory only, with Infra reviewing each app's permissions before installation.
Best,
Yuhang Chang (microg)
________________________________
发件人: haoqing@apache.org <ha...@apache.org>
发送时间: 2026年8月21日 17:33
收件人: dev@maka.apache.org <de...@maka.apache.org>
主题: Re: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
+1 from me. I support re-enabling CodeRabbit and Qodo for apache/maka under the proposed scope.
Best,
Haoqing
> 2026年8月20日 19:43,Lei Yuhan <le...@outlook.com> 写道:
>
> Hi all,
>
> CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
>
> I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
>
> * CodeRabbit: https://github.com/apps/coderabbitai
> * Qodo Code Review: https://github.com/apps/qodo-code-review
>
> Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
>
> The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
>
> If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
>
> Thanks,
> Yuhan
>
> AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
Re: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by ha...@apache.org.
+1 from me. I support re-enabling CodeRabbit and Qodo for apache/maka under the proposed scope.
Best,
Haoqing
> 2026年8月20日 19:43,Lei Yuhan <le...@outlook.com> 写道:
>
> Hi all,
>
> CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
>
> I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
>
> * CodeRabbit: https://github.com/apps/coderabbitai
> * Qodo Code Review: https://github.com/apps/qodo-code-review
>
> Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
>
> The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
>
> If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
>
> Thanks,
> Yuhan
>
> AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
RE: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Lei Yuhan <le...@outlook.com>.
Correction: Yongtao's +1 arrived before my previous message and was not included in my count.
We therefore have two independent explicit PPMC +1s: Yongtao Wang and Kun Li. Kun's replies from two addresses represent the same person and should be counted once.
The request for one or two additional PPMC or mentor views, and the Monday deadline, remain unchanged.
Sorry for the confusion.
Thanks,
Yuhan Lei
(astrohan, @Astro-Han on GitHub)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
RE: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Lei Yuhan <le...@outlook.com>.
Thanks, Kun.
We currently have one explicit PPMC +1. Yongtao raised a question about ASF/Infra expectations for third-party access, and I replied with the public evidence and narrowed the proposal so that Infra will review each app before any installation.
Since these apps require third-party repository access, an explicit view from one or two more PPMC members or mentors would help the INFRA requests. Please reply with +1, an objection, or any condition you think the requests should include.
The proposed scope is:
* file separate INFRA tickets for CodeRabbit and Qodo;
* limit access to apache/maka;
* keep both bots advisory and not required for merging;
* let Infra decide whether each app's permissions are acceptable.
Because the original 72-hour period crosses the weekend, I will keep the discussion open through Monday, August 24, 11:44 UTC.
Thanks,
Yuhan Lei
(astrohan, @Astro-Han on GitHub)
AI use: Codex helped draft this procedural follow-up. I reviewed it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
Re: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Kun Li <ku...@apache.org>.
+1. I support the narrowed proposal and agree to file separate INFRA tickets for CodeRabbit and Qodo.
On 2026/08/20 11:43:46 Lei Yuhan wrote:
> Hi all,
>
> CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
>
> I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
>
> * CodeRabbit: https://github.com/apps/coderabbitai
> * Qodo Code Review: https://github.com/apps/qodo-code-review
>
> Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
>
> The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
>
> If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
>
> Thanks,
> Yuhan
>
> AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org
Re: [DISCUSS] Re-enable CodeRabbit and Qodo for apache/maka
Posted by Yongtao Wang <wy...@apache.org>.
+1
On 2026/08/20 11:43:46 Lei Yuhan wrote:
> Hi all,
>
> CodeRabbit and Qodo stopped reviewing PRs after the repository moved to apache/maka. On PR #3222, new review commands received no response. Both GitHub App installation pages show "Installations and requests are disabled for this account" for the apache organization, so a Maka committer cannot reconnect them directly.
>
> I would like to ask ASF Infrastructure to install both apps with access limited to apache/maka:
>
> * CodeRabbit: https://github.com/apps/coderabbitai
> * Qodo Code Review: https://github.com/apps/qodo-code-review
>
> Both would remain advisory. They would not be required checks and would not count as the independent human approval required for merging.
>
> The repository is public, but both services process repository and pull request data outside ASF infrastructure and need write access to publish reviews. CodeRabbit also requests read and write access to repository contents. I think these permissions are acceptable for this public repository, but Infra should review them before installation.
>
> If there are no objections within 72 hours, I will record the result and file separate INFRA tickets for the two apps, linking this thread.
>
> Thanks,
> Yuhan
>
> AI use: Codex helped investigate the failed integrations and draft this message. I reviewed the facts and take responsibility for the proposal.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
> For additional commands, e-mail: dev-help@maka.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maka.apache.org
For additional commands, e-mail: dev-help@maka.apache.org