![\"The](\"http:\/\/www.rexfeng.com\/blog\/wp-content\/uploads\/2012\/11\/1-pull-req-detail-540x366.png\" "\\"1-pull-req-detail\\"")
The Pull Request detail<\/p><\/div>\n
1. Add the fork’s pull request repo as a remote<\/h3>\n
[cc]$ git remote add xta https:\/\/github.com\/xta\/breakfast-sandwich.git[\/cc]<\/p>\n
You can verify that the remote [cci]xta[\/cci] has been added by running the [cci]git remote[\/cci] command.<\/p>\n
2. Fetch the git data from remote<\/h3>\n
[cc]$ git fetch xta
\nremote: Counting objects: 5, done.
\nremote: Compressing objects: 100% (3\/3), done.
\nremote: Total 3 (delta 0), reused 3 (delta 0)
\nUnpacking objects: 100% (3\/3), done.
\nFrom https:\/\/github.com\/xta\/breakfast-sandwich
\n* [new branch] add-cheese-to-list -> xta\/add-cheese-to-list
\n* [new branch] master -> xta\/master[\/cc]<\/p>\n
3. Checkout the remote branch<\/h3>\n
[cc]$ git co xta\/master
\nNote: checking out ‘xta\/master’.
\nYou are in ‘detached HEAD’ state. You can look around, make experimental
\nchanges and commit them, and you can discard any commits you make in this
\nstate without impacting any branches by performing another checkout.
\nIf you want to create a new branch to retain commits you create, you may
\ndo so (now or later) by using -b with the checkout command again. Example:
\ngit checkout -b new_branch_name
\nHEAD is now at be7c26d… add cheese to ingredients list[\/cc]<\/p>\n
4. Checkout to a new test branch<\/h3>\n
[cc]$ git co -b “test-add-ingredient”
\nSwitched to a new branch ‘test-add-ingredient'[\/cc]<\/p>\n
5. Test the current branch<\/h3>\n
For this step, you would need to perform whatever steps your project deems appropriate before accepting a pull request.<\/p>\n
We can open up [cci]list.txt[\/cci] and see that it now contains cheese:<\/p>\n
[cc]# ingredients list
\n* english muffin
\n* eggs
\n* sausage
\n* cheese[\/cc]<\/p>\n
As the updated ingredients from [cci]xta\/master[\/cci] pass our critiera, we need to merge it back into master branch.<\/p>\n
6. Check your feature branch against master to make sure any merge conflicts happen in your feature branch<\/h3>\n
[cc]$ git rebase master
\nCurrent branch test-add-ingredient is up to date.[\/cc]<\/p>\n
7. Merge feature branch into master<\/h3>\n
First, switch to master branch:<\/p>\n
[cc]$ git co master
\nSwitched to branch ‘master'[\/cc]<\/p>\n
Then merge the feature branch into master.<\/p>\n
[cc]$ git merge test-add-ingredient
\nUpdating 5004985..be7c26d
\nFast-forward
\nlist.txt | 3 ++-
\n1 file changed, 2 insertions(+), 1 deletion(-)[\/cc]<\/p>\n
8. Push your master onto GitHub<\/h3>\n
Great job! We’ve reviewed the feature branch, merged it into master locally. So now, we need to make sure the internet has access to our open source breakfast sandwich that includes cheese.<\/p>\n
[cc]$ git push
\nCounting objects: 5, done.
\nDelta compression using up to 4 threads.
\nCompressing objects: 100% (3\/3), done.
\nWriting objects: 100% (3\/3), 343 bytes, done.
\nTotal 3 (delta 0), reused 0 (delta 0)
\nTo git@github-xtatest:xtatest\/breakfast-sandwich.git
\n5004985..be7c26d master -> master[\/cc]<\/p>\n
When you look at your GitHub repo, you’ll see that the pull request is now closed. Most importantly, our breakfast sandwich has cheese!<\/p>\n
![\"Closed](\"http:\/\/www.rexfeng.com\/blog\/wp-content\/uploads\/2012\/11\/2-closed-request-540x294.png\" "\\"2-closed-request\\"")
Closed Pull Request<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
With a git workflow, you become used to commands like [cci]git add filename[\/cci] and [cci]git commit -m “add filename”[\/cci]. When you maintain an open source project and get a pull request, the exact workflow may get murky. How do you review the pull request work? How do you accept the commit if it passes muster? […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1029],"tags":[1035,1033,338,1030,1034,1031,1032],"class_list":["post-1645","post","type-post","status-publish","format-standard","hentry","category-programming","tag-branch","tag-close","tag-git","tag-github","tag-issue","tag-pull","tag-request"],"_links":{"self":[{"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/posts\/1645","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/comments?post=1645"}],"version-history":[{"count":16,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/posts\/1645\/revisions"}],"predecessor-version":[{"id":1680,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/posts\/1645\/revisions\/1680"}],"wp:attachment":[{"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/media?parent=1645"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/categories?post=1645"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rexfeng.com\/blog\/wp-json\/wp\/v2\/tags?post=1645"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Pull](\"http:\/\/www.rexfeng.com\/blog\/wp-content\/uploads\/2012\/11\/1-pull-request-540x296.png\" "\\"1-pull-request\\"")