dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

This commit is contained in:
Parker Moore 2013-04-26 19:09:11 +02:00
parent d2f364b60c
commit 9a5a702e47
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -41,7 +41,7 @@ Workflow
Here's the most direct way to get your work merged into the project: Here's the most direct way to get your work merged into the project:
* Fork 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` ). * Create a topic branch to contain your change ( `git checkout -b my_awesome_feature` ).
* Hack away, add tests. Not necessarily in that order. * Hack away, add tests. Not necessarily in that order.
* Make sure everything still passes by running `rake`. * Make sure everything still passes by running `rake`.