summaryrefslogtreecommitdiff
path: root/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown')
-rw-r--r--_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown2
1 files changed, 2 insertions, 0 deletions
diff --git a/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown b/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown
index 56e0410..c4d9eb7 100644
--- a/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown
+++ b/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown
@@ -9,6 +9,8 @@ redirect_from: "/writing/less-file-compilation-for-jekyll-github-pages/"
I recently wrote about [migrating my website to GitHub Pages](/writing/migrating-to-github-pages-and-jekyll) and noted that I wasn’t completely satisfied with my deployment workflow. Ideally, [creating a build should be done in a single step](http://www.joelonsoftware.com/articles/fog0000000043.html). As I wrote, my previous build workflow required me to manually compile my [LESS](http://lesscss.org) files before committing if I’d made changes. While my stylesheet doesn’t change often, this method is certainly not ideal.
+<!--more-->
+
Using [Git hooks](http://git-scm.com/book/en/Customizing-Git-Git-Hooks), it’s possible to run a script at certain points during the Git workflow. To take advantage of this in my case, I added a small bash script to `.git/hooks/pre-commit`:
{% gist benburwell/0ef673f6311b5191186e %}