title: Should build folders be included in a git repo?
body: <p>I'm trying to set up a git repository for my bespoke WordPress theme builds, using gulp to compile the code but im struggling to understand how to manage the repo.</p>
  
  <p><strong>The outcome I'm after:</strong></p>
  
  <ol>
  <li>Use a separate repo to pull in my gulp workflow. (Could be housed as a submodule)</li>
  <li>Offer developers full access to my gulp workflow, src and build.</li>
  <li>Push the build folder to remote servers such as production and staging.</li>
  </ol>
  
  <p><strong>Current Scenario</strong></p>
  
  <p>My gulp workflow will be held in a separate repo as it will be used amongst several different builds.</p>
  
  <p>The current workflow I can think of would look like this:</p>
  
  <pre><code>gulp-wp-build -&gt; git repo
  
  src -&gt; git repo
  
  build -&gt; WordPress ready theme not held in a repo
  </code></pre>
  
  <p>Ideally though I'd like to be able to push my code to the production and staging servers through git and I understand that to do this I'd need to do include the build folder inside of my repo. <em>But would including both my src folder and build folder within the repo be overkill?</em></p>
  
  <p>I like the idea of containing everything inside of one repo so other developers can work on the theme later down the line using either their gulp workflow or the one I used for the build. </p>
  
  <p>But really in terms of pushing changes through git I'd only want the build to be pushed live so could I separate this build folder from the repo when pushed to a certain remote?</p>