Skip to content

Commit afc7d8e

Browse files
committed
Merge pull request github#226 from rsese/clarify-issue-to-pull-request
Clarify issue to pull request
2 parents af8d0f0 + 8c4e52d commit afc7d8e

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

content/guides/getting-started.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -389,8 +389,19 @@ the `Location` response header and the `url` field of the JSON response.
389389

390390
GitHub moves fast and the API tries to keep pace, but there are some things you
391391
can do with the API that you can't do on github.com. Using the API, you can
392-
turn an issue into a Pull Request. Let's convert the issue we just created
392+
turn an issue into a Pull Request.
393393

394+
But at this point, we'll need to create a branch called `new-feature`
395+
with at least one commit so it's ahead of the `master` branch:
396+
397+
git clone https://github.com/repos/github/platform-sandbox
398+
git checkout -b new-feature
399+
touch cool-feature.rb
400+
git add cool-feature.rb
401+
git commit -m "Add new feature."
402+
git push origin new-feature
403+
404+
Now let's convert the issue we created in the previous section:
394405

395406
curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \
396407
-d '{ \

0 commit comments

Comments
 (0)