From cdcb92bb38c3ecc3543bdf67ce23c14d0f51d036 Mon Sep 17 00:00:00 2001 From: Coby Chapple Date: Thu, 2 May 2013 21:43:22 +0100 Subject: [PATCH] make these clone instructions behave as blocks --- site/_posts/2012-07-01-contributing.md | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/site/_posts/2012-07-01-contributing.md b/site/_posts/2012-07-01-contributing.md index 473fcf32..90ffe120 100644 --- a/site/_posts/2012-07-01-contributing.md +++ b/site/_posts/2012-07-01-contributing.md @@ -56,12 +56,28 @@ 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//jekyll.git` -* Create a topic branch to contain your change: `git checkout -b my_awesome_feature` +* Clone down your fork: + +{% highlight bash %} +git clone git://github.com//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. * Make sure everything still passes by running `rake`. * 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 does and the why you think it should be merged.