You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ If you do not do one of these three things, when you try to do a git clone, it w
66
66
Let's imagine we're working in groups. If we have everyone pushing to one repo without verifying the quality of the code, things can get messy pretty quick. GitHub fixed this solution with 'Pull Requests.' Basically, you fork a project, make changes to your fork, then you make a Pull Request (PR) back into the original project requesting that some piece of code be added to the original repo. This is how the vast majority of open source code projects work.
67
67
68
68
###Step 2: Make the PR
69
-
* Go to your forked repo on github and click where it says 'Pull Request.'It should show you the file changes you've made and how they differ from the original repo. If it does, click on thesubmit button to submit your pull request.
69
+
* Go to your forked repo on github and click where it says 'Pull Request', and click 'New pull request'.It should show you the file changes you've made and how they differ from the original repo. If it does, click on the'create pull request' button to submit your pull request.
70
70
* Now, I should see your pull request and I can decide if I want to add that code into the main project or not.