+1 On Wed, 24 Jun 2026 at 10:39 AM, Peter Lee <[email protected]> wrote:
> +1 > > - Peter > > On Wed, Jun 24, 2026 at 12:23 PM Ayush Saxena <[email protected]> wrote: > > > +1 > > > > -Ayush > > > > > On 24 Jun 2026, at 9:32 AM, Ritesh Shukla <[email protected]> wrote: > > > > > > +1 this has been useful to me. > > > Regards, > > > Ritesh > > > > > >> On Jun 24, 2026, at 7:00 AM, Ivan Andika <[email protected]> wrote: > > >> > > >> Thanks Wei-Chiu for starting this discussion. > > >> > > >> I’m +1 overall. Copilot can review the long hanging fruits first > > (obvious logic errors, etc) then the reviewer can review with high > > confidence that the low hanging fruits is handled and can focus on the > > higher level logic (i.e. whether it fits to the overall project). > > >> > > >> The caveat is that some reviewers (including me) sometimes skip PR > that > > has not addressed the copilot reviews. So this might backfire on the > review > > velocity as well since the reviewers might not revisit these PRs. > > >> > > >> Let me know what you think. > > >> > > >>>> On 24 Jun 2026, at 05:18, Wei-Chiu Chuang <[email protected]> > wrote: > > >>> > > >>> Should we allow GitHub Copilot to review PR as soon as they are > opened? > > >>> Would it help with review velocity? > > >>> > > >>> This is possible via asf.yaml > > >>> https://github.com/apache/infrastructure-asfyaml#copilot_code_review > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
