Code Review tools
time to read 1 min | 70 words
Originally posted at 1/17/2011
Occasionally I get asked what code review tools I use.
The truth is, I tend to use TortoiseGit’s Log Viewer and just read the history, but I am not leaning toward this baby:
This is really nice!
Comments
That's my way to see how RavenDB is working. Whenever you commit something to the repository, I inspect the changes and try to understand them. This way I can see if it might break my code, and I think I learn something too. Additionally I may see an error on occasion as the one above, and a direct comment on GitHub seemed to be the most appropriate way for reporting.
shouldn't the 't' be a 'w'
;)
The only thing I still need is pull requests on existing issues, then there is nothing that stops me to do the next larger project we tackle with the aid of a private repository in github :)
I like to use Codebase HQ for private team based projects - http://www.codebasehq.com/ - lots of nice features although, I have not seen specific line notes like you are showing here.
Never had a chance to use this, but i keep it bookmarked just in case. http://code.google.com/p/rietveld/
Comment preview