Clarify converting an issue to pull request.

rsese · rsese · commit cdf608dc6844 · 2013-03-07T23:49:42.000-08:00
Running the example as is will result in a 422 error saying
there's no commits between master and new-feature. This adds a
note saying that you need a new-feature branch that's ahead of
master to run the example.
diff --git a/content/guides/getting-started.md b/content/guides/getting-started.md
@@ -380,8 +380,16 @@ the `Location` response header and the `url` field of the JSON response.
 
 GitHub moves fast and the API tries to keep pace, but there are some things you
 can do with the API that you can't do on github.com. Using the API, you can
-turn an issue into a Pull Request. Let's convert the issue we just created
+turn an issue into a Pull Request.
 
+But at this point, if you want to run this example to convert your issue to a
+pull request, you'll need to create a branch called new-feature with at least
+one commit so it's ahead of the master branch. Otherwise, if we try and convert
+the issue to a pull request now, we'll receive `422` error telling us that
+there's no commits between master and new-feature.
+
+If you've created the new-feature branch and made a commit to it, let's convert
+the issue we created in the previous section:
 
     curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \
          -d '{ \
