Dave Reid

And taxonomy terms And users And anything that might be embedded in the WYSIWYG body field And comments

Note that using D7 composer_manager works differently than D8 composer_manager. Would this need to be taken into account?

cc @ericduran

An alternative seems to be https://bitbucket.org/davereid/drush-casperjs/src/4d9f4119f830899cf9fd2c6ce4e38fa43bb8b184/drupal.js?at=master#cl-162

Also see https://bitbucket.org/davereid/drush-casperjs/overview

The README.md is documented, but I guess my confusion is the projects I have encountered so far have not had a maintained README.md of the patches. This has been confusing...

I'll suggest another alternative - projects should always have a make file if possible. Make files are great at documenting patches in a standardized format (You must define which module...

Maybe something like a patches.make file? ``` ; Add Migrate support for redirects. ; @see https://drupal.org/comment/5699446#comment-5699446 projects[redirect][patch][] = "https://drupal.org/files/1116408_26_migrate_redirect.patch" ``` This is machine-readable and could easily be parsed by Drush....

The patches.make approach seems to have merit and agreement, yay. I can make start here by providing an empty file, documentation for what to add, and integrate it with Drush...

Maybe we should use https://bitbucket.org/davereid/drush-casperjs/src/c64819c648587f35278bbdf27a854829a89a3dac/common.js?at=master#cl-59 ? I expanded to a randomString() and randomName() functions to match more what Drupal core provides with DrupalTestCase.