git push origin master
{endsnip}
-Then, if the pull request was made from master but should also apply to the stable branch (because it's a bug fix), then cherry-pick the commit back to the correct branch. *There may be more than one commit in a pull request.* If this is the case, make sure you do them in the correct order. If you are picking into a release branch consult with TimT and TJ first.
+Then, if the pull request was made from master but should also apply to the stable branch (because it's a bug fix), then cherry-pick the commit(s) back to the correct branch. *There may be more than one commit in a pull request.* If this is the case, make sure you do them in the correct chronological order. If you are picking into a release branch consult with TimT and TJ first.
+
+One way to find the commit hashes is from the github.com website. While viewing the pull request click on the "Commits" tab and you will see a list.
+
+Another way to get the commit hashes is by running "git log" while you still have the master branch checked out. You are searching for the individual commit(s) in the pull request, NOT the commit of the merge you just did to master. Search for appropriate keywords from the pull request, or for the committer's username, or "github.com". Make sure you get all commits contained in the pull request, and in the right chronological order. It's probably better to get them using the first method (i.e. directly from github.com).
+
{snip: Example: Cherry-pick the commit(s) back to stable (V8_8-branch in this example)}
git checkout V8_8-branch
git pull
-git cherry-pick <commit-hash-1> # ADD THE GITTRAC TICKET NUMBER TO CHERRY-PICK COMMIT MESSAGE!!
-git cherry-pick <commit-hash-2> # ADD THE GITTRAC TICKET NUMBER TO CHERRY-PICK COMMIT MESSAGE!!
+git cherry-pick <commit-hash-1>
+git cherry-pick <commit-hash-2>
...
git push origin V8_8-branch
{endsnip}
