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

make these clone instructions behave as blocks

This commit is contained in:
Coby Chapple 2013-05-02 21:43:22 +01:00
parent 6cc77dfeee
commit cdcb92bb38
1 changed files with 19 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
site/_posts/2012-07-01-contributing.md
View File

@ -56,12 +56,28 @@ 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:
* Create a topic branch to contain your change: `git checkout -b my_awesome_feature`
{% highlight bash %}
git clone git://github.com/<username>/jekyll.git
{% endhighlight %}
* Create a topic branch to contain your change:
{% highlight bash %}
git checkout -b my_awesome_feature
{% endhighlight %}
* 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`.
* If necessary, rebase your commits into logical chunks, without errors. * If necessary, rebase your commits into logical chunks, without errors.
* Push the branch up: `git push origin my_awesome_feature` * Push the branch up:
{% highlight bash %}
git push origin my_awesome_feature
{% endhighlight %}
* Create a pull request against mojombo/jekyll and describe what your change * Create a pull request against mojombo/jekyll and describe what your change
does and the why you think it should be merged. does and the why you think it should be merged.