This post could also be titled “How an update to the Github app combined with a change to how my project compiles Sass rendered me incapable of committing my code.”
The last time I wrote about using Sass in my WordPress theme, I was still using a Brackets plugin to compile it into CSS. I was restricted in what I could do, because the Brackets SASS plugin uses libsass, a C/C++ implementation of Sass, which natively runs on Ruby. The advantage here is that I didn’t need to install Ruby or the Sass gem to compile my code; the disadvantage is that it is not up to date with the current version of Sass, and that includes the multiple assignment usage of the @each directive.
Well, I decided that I wanted to run the latest and greatest version of Sass, and that meant installing Ruby. I won’t walk you through the installation process — Sass’s install page can help you better than I can for that.
A conflict of interest
When the Github app restarted, it took forever to load up. When it finally did, I was greeted with this:
I assumed it was something wrong with the app itself, not with my project. After all, Grunt was running fine and compiling what I wanted it to compile. It couldn’t possibly be anything in my code. Could it?
As it turned out, it was. You see, when you install Grunt, it’s on a per-project basis. And Grunt sets up a directory structure inside each project, starting with the top-level directory of /node_modules. I have since discovered that it’s generally a good idea not to commit that into git. So I added this to my .gitignore file:
Since making that change, the Github app has behaved wonderfully since.