Adam Ross

1. Copy composer.json, composer.lock, and vendor/ into the package root. 2. Copy the docroot one level deeper than root of package.

ShipIt maintainer is focused on very git-centric deployments. We do not want to do that for the mechanisms we most commonly use capistrano to achieve. There are other grunt-deploy plugins,...

A separate release repository makes lots of sense, with possible value in a grunt plugin like https://www.npmjs.com/package/grunt-git-deploy. That would allow us to have some unification across Acquia, Pantheon, and other...

I've had composer validate on my mind, and parallel-lint looks awesome. The problem here is it moves control over validation outside grunt configuration & execution. Can we parameterize the configuration...

We can wrap this in a compatibility mode config, but here are the parts to pay attention to: 1. `grunt watch` (I suspect broken anyway) 2. `grunt git-setup` (currently installs...

This was uncovered as part of the work done in #214

Hi @csegarra, thank you for your contribution! I need to think about this a bit because my planning around grunt-drupal-tasks configuration handling was more toward decoupling it from GDT itself,...

Possibly related, I am unsure why we have [`copy:defaults`](https://github.com/phase2/grunt-drupal-tasks/blob/master/tasks/copy.js#L38) alongside the [`symlink:sites` task of our `scaffold` operation](https://github.com/phase2/grunt-drupal-tasks/blob/master/tasks/scaffold.js#L39). If I read this right, the build process is copying the default settings...

Does this deprecate #323?

Re-triggering travis tests.