Pull Requests are great for understanding the larger thinking around a change or set of changes made to a repo. Reading pull requests are a great way to quickly “grok” a project as, instead of small atomic changes to the source, you get larger groupings of logical changes. Analogous to organizing the lines in your code into related “stanzas” to make it easier to read.
I find myself looking at a file or a commit, and I wonder if there is a way to backtrack the commit to the Pull Request that originally created it. That Pull Request would have been merged eventually, but not necessary with a merge-commit.
You can just go to GitHub and enter the SHA into the search bar, make sure you select the "Issues" link on the left.
UPDATED 13 July 2017
Via the GitHub UI there is a now a really easy way to do this. If you are looking at a commit in the list of commits in a branch in the UI, click on the link to the commit itself. If there is a PR for that commit and it wasn’t added directly to the branch, a link to the PR listing the PR number and the branch it went into will be directly under the commit message at the top of the page.
If you have the commit SHA and nothing else and don’t want to go digging around for it, just add
/commit/[commit SHA] to the repo url, and you will see the commit page, with the PR link if it exists.
For example, if the SHA is 52797a7a3b087231e4e391e11ea861569205aaf4 and the repo is https://github.com/glimmerjs/glimmer-vm , then go to https://github.com/glimmerjs/glimmer-vm/commit/52797a7a3b087231e4e391e11ea861569205aaf4
Answered By – RustyToms