Skip to main content

Git for Authors

Robert A. Beezer, David Farmer

Appendix E Cheat sheet for managing pull requests

You are one of the people in charge of a GitHub repository. Below are the typical steps to evaluate pull requests.
List E.0.1.
  1. Click on the Pull requests tab, and then choose a pull request.
  2. If there are merge conflicts, write a brief message and click Comment.
    Now there is nothing else to do until you get an email either replying to your comment, or telling you that the pull request has been updated.
  3. Click on the Files changed sub-tab, and carefully look at all the changes. If there are any errors or violations of the official style for the project, click back to Conversation and leave a helpful Comment.
  4. If the changes look reasonable, then you have to actually check that the new material functions as advertised. Go to your laptop and do:
    git checkout master
    git pull upstream master
    Then click back to Conversation and click on command line instructions. Copy and paste those into the command line. They will look something like this:
    git checkout -b fredstro-solutions-chap-6 master
    git pull https://github.com/fredstro/calculus.git solutions-chap-6
  5. Check their contribution: run latex, or compile the code, or whatever is appropriate.
  6. If you aren’t happy with what you see, leave a helpful comment.
    But if everything looks good, click Merge pull request, leave a comment if appropriate, and then click Confirm merge.
  7. You are done, except don’t forget to git checkout master and then pull in the new material.
PrevTopNext