January 05, 2017
One of our newest OptinMonster developers has already made a big splash by introducing even more automation to our development flow. For the past two years (TWO!) this has been our usual conversation after pushing some changes:
The changes you pushed aren’t working.
Do I need to run anything after pulling this down?
composer installin the core plugin and theme.
npm installin the theme.
gulp scriptsin the theme.
Ah! There we go!
It was time to put an end to it. The new dev created a few git hooks, installed with a script, that run all of the necessary build steps after a pull from our GitHub repository. Only problem is the hooks don’t work if you’re using Tower or any other GUI for git. Luckily the fix is simple. Add this to the very top of all of your git hook scripts:
This give Tower the correct paths to find whatever scripts you use in your git hooks. In our case it was
Hi! My name is J. Aaron Eaton. I help create amazing web experiences. You should follow me on Twitter