Actually, the regular gulp task cleans and the gulp build task doesn’t.
I’d probably make a new task in the gulpfile just to copy everything over if you really wanted a main.min.css file, but why not just check /dist/ into version control?
edit: oops, sorry - I read it wrong and thought you were saying that gulp build ran the clean task! You were correct that that is the difference.
The only reason I don’t want to track the entire dist folder is because of merge conflicts. By only tracking the build or production file versions that would cut down on those issues.
I see now that gulp build --production does create the assets.json file and builds new file versions but their filenames are randomized, and I wouldn’t be able to track those. Unless I do an exclude.
@austin: Thanks, I’m seeing that feature now. With this setup is there a way to build a main.min.css type file rather than main.css being the one I check into source?
Committing that while working on a project with other developers can cause quite a few merge conflicts. Committing only on build would cut that down.
@emaildano Committing “binaries” to a project is going to cause you trouble no matter what. So I definitely recommend seeking alternate deployment options that do not rely on committing compiled files to the repo.