One possible harm is if copilot points out things that are obvious - say that an emailAddress property will have type “String” even those it is stored in a Map<String, Object> - and the PR author adds over-defensive coding just to make the review comments go away.
I’m not saying that Copilot review wouldn’t be useful. Just an anti pattern to watch out for. One of the best contributions a reviewer can make is to look for things that are missing - say a change in documentation when a UDF is added, based on similar PRs in the past - but I don’t know whether Copilot can do those things. > On Mar 25, 2026, at 8:19 AM, Mihai Budiu <[email protected]> wrote: > > I don't think they will alleviate anything, but they cannot harm. > > Mihai > > > ________________________________ > From: Cancai Cai <[email protected]> > Sent: Wednesday, March 25, 2026 6:21 AM > To: [email protected] <[email protected]> > Subject: [DISCUSS] Enable Copilot review? > > Hi everyone, I know everyone in the Calcite community is very busy. With the > LLM field becoming increasingly popular, I'm wondering if copilot reviews > could help alleviate some of the review pressure. > > What are your thoughts on this? > > Best wishes, > Cancai Cai.
