Ask HN: What are the best tools for code reviews?
21–30 of 55 posts
Re: Ask HN: What are the best tools for code reviews?
#22 git log --pretty=full --reverse --show-notes=* -p --abbrev-commit origin/master..
Coupled with a "good diff highlighter", i.e. `diff-highlight | less --tabs=4 -RFX`… I'm set.I've yet to see a tool that allows me to review all commits as well as code, as easily.
I don't only review a branch as a whole, i.e. `git diff master`, or "here's the diff" from a pull request… but I also review each commit individually (and rebase/amend them when required), as commits need to be in tip-top shape to end up going into master.
Re: Ask HN: What are the best tools for code reviews?
#23Gerrit: https://www.gerritcodereview.com . Hands-down.
(To my eye Gerrit seems like it was written by people who wanted git to work like svn.)
Re: Ask HN: What are the best tools for code reviews?
#24The problems I have with code reviews are people problems, not tool problems. Tools cannot solve those.
The history of software has quite a few examples where software solves people problems
Re: Ask HN: What are the best tools for code reviews?
#25Phabricator https://www.phacility.com
The only plus is the integration with linters. beside that, "native" bitbucket/github/gitlab PRs are way better
Re: Ask HN: What are the best tools for code reviews?
#26My favorite tool is a Microsoft internal tool called CodeFlow. If you don't want to work for them just to have a great code review experience, I recommend https://reviewable.io . Very nice!
Isn't CodeFlow similar to the code review functionality that's now integrated in Visual Studio?
Re: Ask HN: What are the best tools for code reviews?
#27Re: Ask HN: What are the best tools for code reviews?
#28My favorite tool is a Microsoft internal tool called CodeFlow. If you don't want to work for them just to have a great code review experience, I recommend https://reviewable.io . Very nice!
1) All accessible via a browser instead of Desktop App. 2) PRs are all queued up nicely and easily searchable in said browser instead of littered all over a folder in my email 3) PRs can have rules that don't allow merging without reviewers having accepted the change. CodeFlow seems to ignore this in my experience and 'required' reviewers are more just suggestions and people just check in their code whenever anyways.
It's entirely possible my team, myself included, don't understand how to properly use CodeFlow though so take my opinion with boat load of salt. Similarly, I'm sure my third issue could be fixed by improving our review process as well, rather than switching tooling.
Re: Ask HN: What are the best tools for code reviews?
#29Gerrit: https://www.gerritcodereview.com . Hands-down.
Re: Ask HN: What are the best tools for code reviews?
#30https://gitmate.io - Gitmate is made by a friend of mine and it's pretty good. It uses coala [1] underneath (coala is a unified static code analysis tool that supports 100+ languages; I'm a maintainer, so shoot me any questions you might have about coala). Gitmate is much more than just static code analysis and review suggestions. It supports automatic issue triaging, rebases, labeling, identifying human reviewers, a…
How is issue triaging related to code reviews? Trying to imagine how that is useful