From 8944cdf544db94c988a439ee339d8ef02b61d2e6 Mon Sep 17 00:00:00 2001 From: andrewhavens Date: Wed, 20 Nov 2013 21:45:05 -0800 Subject: [PATCH] Update link to example Rakefile to point to specific commit. The link was pointing to the latest version of the file which had been changed and no longer provided the intended example. --- site/docs/deployment-methods.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/docs/deployment-methods.md b/site/docs/deployment-methods.md index 41c5472e..b8ee5ab6 100644 --- a/site/docs/deployment-methods.md +++ b/site/docs/deployment-methods.md @@ -76,7 +76,7 @@ laptops$ git push deploy master ### Rake Another way to deploy your Jekyll site is to use [Rake](https://github.com/jimweirich/rake), [HighLine](https://github.com/JEG2/highline), and -[Net::SSH](http://net-ssh.rubyforge.org/). A more complex example of deploying Jekyll with Rake that deals with multiple branches can be found in [Git Ready](https://github.com/gitready/gitready/blob/en/Rakefile). +[Net::SSH](http://net-ssh.rubyforge.org/). A more complex example of deploying Jekyll with Rake that deals with multiple branches can be found in [Git Ready](https://github.com/gitready/gitready/blob/cdfbc4ec5321ff8d18c3ce936e9c749dbbc4f190/Rakefile). ### rsync