title: What is the recommended way to review pull requests on GitHub?
body: <p>Let's say that a contributor on a project submits a pull request and I need to compile the code in order to make sure that it fixes the issue. In this scenario, I usually copy the changes that the author made into my local repo, run everything and make sure it works, merge the PR, and run <code>git pull</code> to update my local repo.</p>
  <p>But I just discovered that PR's result in a new branch. So I guess it would be better to run <code>git pull</code> and <code>git checkout &lt;branch&gt;</code> locally, run the code and make sure it fixes the issue, then merge the PR and delete the branch.</p>
  <p>What about the scenario in which a (non-contributor) forks a repo, makes changes to the main branch of his forked repo, sets the upstream to the original repo, and submits a PR? Does this result in a new branch on the original repo that I can checkout locally in order to test out the proposed changes?</p>