Commit 9a5a702e authored by Parker Moore's avatar Parker Moore

When one clones one's fork of Jekyll, one should not use the readonly git://...

When one clones one's fork of Jekyll, one should not use the readonly git:// protocol. Instead, use SSH.
parent d2f364b6
......@@ -41,7 +41,7 @@ Workflow
Here's the most direct way to get your work merged into the project:
* Fork the project.
* Clone down your fork ( `git clone git://github.com/<username>/jekyll.git` ).
* Clone down your fork ( `git clone git@github.com:<username>/jekyll.git` ).
* Create a topic branch to contain your change ( `git checkout -b my_awesome_feature` ).
* Hack away, add tests. Not necessarily in that order.
* Make sure everything still passes by running `rake`.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment