https://github.com/apache/ozone/pull/10751 <https://bitli.pro/2Qom7_53a956e2>
On Tue, Jul 14, 2026 at 12:17 PM Gargi Jaiswal <[email protected]> wrote: > +1 > > On Tue, Jul 14, 2026 at 2:43 AM Wei-Chiu Chuang <[email protected]> > wrote: > > > I don't see an option to implement that. Though we can make it review for > > published PR, not draft ones. > > > > > > > https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#copilot-code-review > > > > On Mon, Jul 13, 2026 at 2:04 PM Peter Lee <[email protected]> wrote: > > > > > Actually, I find this a little annoying, as Copilot reviews on every > > push. > > > I’d suggest changing it to: request a Copilot review when the PR is > > opened, > > > and make any following Copilot reviews manual. > > > > > > On Fri, Jul 10, 2026 at 8:52 AM Siyao Meng <[email protected]> wrote: > > > > > > > +1 > > > > > > > > I see a ticket has been filed for this: > > > > https://issues.apache.org/jira/browse/HDDS-15692 > > > > > > > > Patch raised just now: https://github.com/apache/ozone/pull/10705 > > > > > > > > -Siyao > > > > > > > > On Tue, Jun 23, 2026 at 11:00 PM Ashish kumar <[email protected]> > > > wrote: > > > > > > > > > +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] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
