In any open or closed source project, there's nothing as important as the review process is to ensure quality control. GitHub provides several tools that are helpful in inspecting branches and commits which are useful. As a lead developer of Popcorn.js I often get asked to do code reviews by my peers and contributors. I prefer using GitHub to do these reviews, but there's always been this one little annoyance that has had me grumbling.
Compare view is a useful tool provided by GitHub that will clearly display what has changed in a projects code over a series of commits. This is invaluable when there are lots of reviews to do and little time to do them in. Compare view, while being incredibly useful, fails (IMHO) when it comes to one important thing: actually getting to a compare view. GitHub does provide a couple ways to do it, but they are not very easy to use.
It involves navigating to a user's list of branches, and selecting the branch you want to compare. This opens a compare view for that branch, against that user's base branch. After that, if you want to compare the selected branch to a branch on another user's account, you must click the button with the name of the branch and enter in the username and branch from there. This is clunky and non-intuitive. I had no idea this method even existed, because there's no documentation for it, AFAIK.
The second way to open a compare view involves some URL hacking. Lets take popcorn-js for example. I have a "develop" branch for popcorn I use for all reviews. Now imagine that Dave Seifried pushes a branch to his account, then asks me to review his commit(s). The standard url for any branch on GitHub is: "www.github.com/<userName>/<projectName>/tree/<branchName>". So, lets pretend Dave has asked me to review "www.github.com/dseif/popcorn-js/tree/t581". First thing I'd do is navigate to that branch's page using the previous URL. To compare that to my develop branch I can change the URL in the address bar to: "www.github.com/dseif/popcorn-js/compare/cadecairos:develop...t581".
The actual coding of the tool was pretty simple, but not without its annoyances. I had never created a bookmarklet before so I needed to read up on how they're formatted. Being super lazy also had me searching for tools that I could drop my code into and it would generate the bookmarklet for me. These weren't that hard to find. The annoyances came from having to make changes, "crunch" the code, drag it to the bookmark toolbar and then test. This whole process can be annoying. (Maybe I should make a bookmarklet bookmarklet?)
Since I've released the code on GitHub, I've added in configurable defaults by project. This means if I want to set the default account and branch to compare against for popcorn-js to cadecairos:develop, I just fill in the base branch and target user to what I want and hit "set defaults". This saves the values to local storage, so the next time I use the bookmarklet it will use these values when it opens. As I said this works for multiple projects so if you contribute to different repos, you can set defaults for each one. ( just don't clear your cache ;) )
ComareMarklet <---Drag this to your bookmark toolbar to save!