Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitdb82d13

Browse files
committed
last minor edit to PR section
1 parent8b9dd82 commitdb82d13

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff 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
6666
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.
6767

6868
###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.
7070
* Now, I should see your pull request and I can decide if I want to add that code into the main project or not.
7171

7272
##Contributions

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp