6 ms·
Automated linting? Then the reviewers can focus on actually reviewing? Other than that, for a while we tried the policy that if a commit you reviewed broke som
by guitarbill 10y ago
Automated linting? Then the reviewers can focus on actually reviewing?
Other than that, for a while we tried the policy that if a commit you reviewed broke something, the reviewer had to fix it, not the committer. It doesn't really work though, as you might expect.
Edit: I should point out that I'm convinced the main benefit of code review is that your team knows what code you've worked on and what you've changed. Catching mistakes is a nice bonus, but this kind of information transfer is a huge productivity boon.