@@ -39,13 +39,8 @@ maintainers to love you. :heart:*
3939
4040## Submitting a Pull Request
4141
42- - Read the article [ "Using Pull Requests"] ( https://help.github.com/articles/using-pull-requests )
43- on GitHub.
44-
45- - When you submit a pull request (PR), make sure your topic branch is selected
46- on the right-hand side of the Pull Request Preview page, like this:
47-
48- ![ choosing pull request branch] ( https://github-images.s3.amazonaws.com/help/change-branches.png )
42+ - Read the GitHub Guide on [ Forking] ( https://guides.github.com/activities/forking/ ) , especially the part about
43+ [ Pull Requests] ( https://guides.github.com/activities/forking/#making-a-pull-request ) .
4944
5045- Remember, pull requests are submitted * from* your repo, but show up on the
5146 * upstream* repo.
@@ -82,7 +77,9 @@ be fine.
8277First, you'll need a GitHub account, which is totally free. You can sign up
8378[ here] ( https://github.com/signup/free ) .
8479
85- Next, browse the [ GitHub Help site] ( https://help.github.com ) .
80+ Next, browse the [ GitHub Help site] ( https://help.github.com ) and the
81+ [ Github Guides] ( https://guides.github.com/ ) . The Help Site is more technical, and the
82+ Guides are very easy to understand tutorials.
8683
8784You'll want to read about
8885[ forking] ( https://help.github.com/articles/fork-a-repo ) and then make your own
@@ -98,10 +95,8 @@ anyone who wants to contribute do so. His email is behind that profile link.
9895
9996# Closing
10097
101- If you haven't taken the time to go through the Git Immersion lab.
102-
103- Do it. It's worth it no matter how much git-fu you have.
104- http://gitimmersion.com
98+ If you haven't taken the time yet, go through the [ Git Immersion lab] ( http://gitimmersion.com )
99+ at < http://gitimmersion.com > . Do it. It's worth it no matter how much git-fu you have.
105100
106101Also, [ Pro Git] ( http://git-scm.com/book ) is a great (and free!) book about Git.
107102
0 commit comments