I would argue that you avoid striving for a specific GitHub solution. Instead, you can review the code using traditional tools. The most reliable is the git command line. Send the remote branch to the local computer, and then:
> git log -p -n 1 COMMIT_ID -- INTERESTING_FILE(s)
Example:
> git log -p -n 1 abcdef -- foo.txt bar.txt
-p to get the patch-n 1 for single commit-- to start the file listCOMMIT_ID can also be a tag name, branch name, and anything you like to target your commits.
On many systems, you can scroll up / down using the less pagination tool; often out of the box.
And more convenient options on the manual pages: https://www.kernel.org/pub/software/scm/git/docs/git-log.html
As an alternative, I believe that GUI tools like [ gitk ] will be able to handle all of these buffering / scrolling. You will get maximum productivity when working at the local level. Although this can be obtained using Remote Desktop and / or Remote x, there is often too much lag when all this is transmitted over a network connection.
Note. I don't use gitk often, so I cannot be 100% sure of its ability to handle very large files. Please let me know if this is not an option in the comments.
source share