From d6ad07ac92d8cbd8987fd4ab64c527df12f1b94f Mon Sep 17 00:00:00 2001
From: Jared Rewerts <jared.rewerts@edmonton.ca>
Date: Tue, 18 Jun 2019 12:01:46 -0600
Subject: [PATCH 1/2] Added developer setup instructions.

---
 README.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/README.md b/README.md
index bf021040..362182ab 100644
--- a/README.md
+++ b/README.md
@@ -94,3 +94,33 @@ npm install github-api
 [npm-package]: https://www.npmjs.com/package/github-api/
 [unpkg]: https://unpkg.com/github-api/
 [travis-ci]: https://travis-ci.org/github-tools/github
+
+## Contributing
+
+We welcome contributions of all types! This section will guide you through setting up your development environment.
+
+### Setup
+
+1. [Install Node](https://nodejs.org/en/) version 8,10 or 11. It can often help to use a Node version switcher such as [NVM](https://github.com/nvm-sh/nvm).
+2. Fork this repo to your GitHub account.
+3. Clone the fork to your development machine (`git clone https://github.com/{YOUR_USERNAME}/github`).
+4. From the root of the cloned repo, run `npm install`.
+5. Email jaredrewerts@gmail.com with the subject **GitHub API - Personal Access Token Request**
+
+A personal access token for our test user, @github-tools-tests, will be generated for you.
+
+6. Set the environment variable `GHTOOLS_USER` to `github-tools-tests`.
+
+`export GHTOOLS_USER=github-tools-tests`
+
+7. Set the environment variable `GHTOOLS_PASSWORD` to the personal access token that was generated for you.
+
+`export GHTOOLS_PASSWORD={YOUR_PAT}`
+
+**NOTE** Windows users can use [this guide](http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-windows-command-line-and-registry/) to learn about setting environment variables on Windows.
+
+### Tests
+
+The main way we write code for `github-api` is using test-driven development. We use Mocha to run our tests. Given that the bulk of this library is just interacting with GitHub's API, nearly all of our tests are integration tests. 
+
+To run the test suite, run `npm run test`.

From a8b9f620c97916acf0d1ca787104614df5cdb85f Mon Sep 17 00:00:00 2001
From: Jared Rewerts <jaredrewerts@gmail.com>
Date: Tue, 8 Oct 2019 22:23:00 +0900
Subject: [PATCH 2/2] Fixed test user name.

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 362182ab..5e5f527f 100644
--- a/README.md
+++ b/README.md
@@ -107,11 +107,11 @@ We welcome contributions of all types! This section will guide you through setti
 4. From the root of the cloned repo, run `npm install`.
 5. Email jaredrewerts@gmail.com with the subject **GitHub API - Personal Access Token Request**
 
-A personal access token for our test user, @github-tools-tests, will be generated for you.
+A personal access token for our test user, @github-tools-test, will be generated for you.
 
-6. Set the environment variable `GHTOOLS_USER` to `github-tools-tests`.
+6. Set the environment variable `GHTOOLS_USER` to `github-tools-test`.
 
-`export GHTOOLS_USER=github-tools-tests`
+`export GHTOOLS_USER=github-tools-test`
 
 7. Set the environment variable `GHTOOLS_PASSWORD` to the personal access token that was generated for you.