On Thursday, September 25, 2014 06:36:30 AM David Roden wrote: > GitHub might get unwieldy if you try to locate a > specific comment
It supports deep links to comments. The date in the comment display is the link. Example: https://github.com/toad/fred-staging/commit/19c442ef1a1dc904c314675c3a17ce9c8ee6f853#commitcomment-7927272 > or simply want to continue where you left off on a page > with hundreds of changed files. Just store the commit hash of the last commit you reviewed? This is assuming you're reviewing on a per-commit base. If you want to review a multi-commit diff, I would suggest you: - do it locally by cloning - if you want to commit on a particular line, use git blame to find out which commit that line came from - go to the page of that commit on Github and comment there. This also works using the commit hash. Example - notice INSERT_HASH_HERE: https://github.com/toad/fred-staging/commit/INSERT_HASH_HERE
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
