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.markdown1
1 files changed, 1 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 c5e66f9..6762b7c 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
@@ -4,6 +4,7 @@ title: LESS File Compilation for Jekyll and GitHub Pages
description: Git’s pre-commit hook allows one-click static site deployment — including LESS file compilation — to GitHub pages.
category: writing
date: 2014-05-31 00:00:00
+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.