2.0
@hn_a962c6
28 days ago
Copilot Code Reviews are Actions workflows. Just privileged ones you can't edit the YAML for. They even litter your Actions tab list and Deployment environments.
GitHub feature that auto-reviews pull requests, posting inline comments with suggested fixes; can be requested manually or set to review all new PRs.
@hn_a962c6
28 days ago
Copilot Code Reviews are Actions workflows. Just privileged ones you can't edit the YAML for. They even litter your Actions tab list and Deployment environments.
@hn_51f535
about 1 month ago
But copilot code review agent is pretty good at catching when code and comments diverge (even in unrelated documentation files).
@hn_4bd881
about 1 month ago
Yea, but copilot review is useless. The noise it generates easily costs that much in wasted time.
@hn_baad54
about 1 month ago
So the solution is to stop doing code reviews and just YOLO-merge everything? After all, everything is fucked already, how much worse could it get? For the record, there are examples where human code review and design guidelines can lead to very low-bug code. NASA published their internal guidelines for producing safety-critical code[1]. The problem is that the development cost of software when using such processes is too high for most companies, and most companies don't actually produce safety-critical software. My experience with the vast majority of LLM code submitted to projects I maintain is that it has subtle bugs that I managed to find through fairly cursory human review. The copilot code review feature on GitHub also tends to miss actual bugs and report nonexistent bugs, making it worse than useless. So in my view, the death of the benefits of human code review have been wildly exaggerated. [1]: https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Dev
@hn_f8fb0d
about 1 month ago
My guess is that they're moving to a spot where they can pitch an LLM "doing something" as an action, and copilot is their first move. I don't see it as crazy to think of a "copilot code review" in a similar way to other build actions. But also - enterprise accounts already have budget assigned to github actions, and this allows them to start billing right away without having to actually get (or allow) businesses to evaluate the return of having copilot do code reviews. So seems like it's a mix of immediate incentives and long term architecture. I don't like it, though. If I were an enterprise my first response would be to turn it off.