We have a
gulpfile.js in the root of very project that has an automated
workflow. Usually we only use Gulp to do a handful of automated and repetitive
tasks, which makes our gulpfiles easy to read. It’s always worth having a look
gulpfile.js in a project as it’ll tell you everything you need to know
about the automation that’s present in the build.
By default we have our own gulpfile.js and corresponding package.json up on BitBucket. The team at Crowd tends to use this simple but fairly fully featured file as a starting point for projects.