Re:A tiny tool to make using GitHub for code reviews a tiny ...
by andrewcooke on Thursday January 05, 2012 @07:18AM
(#3428432)
does code review need to be tied to your scm? i can see how it means slightly less work, but what's the minimum infrastructure you need to make it independent of the scm? i would guess it's little more than some bash and procmail scripts (assuming unix).
[ Parent
| on HN ]
Re:A tiny tool to make using GitHub for code reviews a tiny ...
by obtu on Thursday January 05, 2012 @09:41AM
(#3428813)
The kernel model (git format-patch, git send-email, git am --signoff) might be automated a little bit more with procmail scripts that auto-apply patches sent to a mailing list once they've been acked as needing no further revision. That workflow has the benefit of decentralisation, but I don't think other SCMs have the equivalent commands. Widespread support is particularly necessary for the people who initiate reviews, since they are more numerous and less likely to have specific tools installed.
Re:A tiny tool to make using GitHub for code reviews a tiny ...
by breckinloggins on Thursday January 05, 2012 @11:49AM
(#3429344)
It doesn't have to be, but integrating with GitHub's line- and commit-level comments and pull requests certainly helps incorporate code reviews into the history of the project and each file in it.