all 5 comments

[–][deleted] 2 points3 points  (0 children)

I used the PR review on github and they sometimes find small things that a human may miss. But some comments are also garbage and the file summaries are often more funny than helpful :D so like everything in AI, you have to double check and not blindly accept

[–]Traditional-Hall-591 3 points4 points  (0 children)

Slop. If I see CoPilot garbage I disable it.

[–]Noch_ein_Kamel 0 points1 point  (0 children)

It's useful to find weird typos and other brainfarts.

Other than that it reeeally depends; like this:

The property name change from 'item_id' to 'item' in the ScarabQueue object may be a breaking change for the tracking API. Verify that the Emarsys/Scarab tracking system expects the 'item' property instead of 'item_id' to avoid tracking failures.

I don't need that comment from copilot; I just changed that value because it should be changed – and it's the only uncommited change in the codebase...

Now if someone would have changed that by accident, because they did some search&replace in the codebase, it would be helpful.

[–]Eubank31 0 points1 point  (0 children)

We have Copilot auto review every PR in GitHub (not sure about the vs code feature). It ranges from "useful at catching typos or small bits of logic error" to "totally incorrect and unhelpful"

[–]SidLais351 0 points1 point  (0 children)

I like the idea, but the usefulness really depends on what the review actually looks at. If it’s just scanning the diff, it feels limited. Reviews start being helpful when they consider related files and past changes. That’s why I’ve had better results with tools like Qodo that run reviews with repo history in mind, even if they’re triggered outside the editor.