When someone submits a change via GitHub, an Evergreen developer should follow these steps to review it:

1. If you haven't yet, add the main Evergreen repo (on GitHub) as a remote
   1. git remote add github-evergreen https://github.com/evergreen-library-system/Evergreen.git
2. Fetch the pull request branch into a new local branch
   1. git fetch origin pull/[PULL_REQ_NUMBER]/head:[BRANCHNAME]
3. Test build the changed AsciiDoc file
   • asciidoc -a data-uri -a icons -a toc -d book -o OUTPUT_FILE ASCIIDOC_FILE
   • Ignore warnings for not finding any image files, but be sure to review any included images on GitHub before committing them
   • Also look for other AsciiDoc warnings or errors
4. Make any corrections (via additional commits, if needed)
5. Update your local master branch to reflect any changes from "origin"
   1. git checkout master; git fetch origin; git pull origin master
6. Cherry-pick each commit from the pull request into your local master branch, adding your sign-off
   1. git cherry-pick -s [commit-hash]
      • (If the GitHub author does not match the author's identity in git.evergreen-ils.org, consider fixing it with git commit --amend --author="NAME <email>")
      • Include the relevant Launchpad bug number somewhere in the commit message
        • Example: "Resolves LP#1234567"
      • Out-dent the sign-off line (if present)
      • Add newlines to long commit messages, making lines about 72 characters long
7. When you are confident your commits are ready: git push origin master
8. Backport to previous EG versions as appropriate
9. Email docs list and/or pull requester to say it is done (or with other feedback)
10. Close pull request on GitHub