Problem/Motivation
I've been maintaining my contrib projects using https://github.com/ddev/ddev-drupal-contrib for some time now, and have just been leaving the .ddev folder uncommitted.
But now that DDEV has become the gold standard for Drupal local development, I feel it is now safe to commit the .ddev folder to the project (as recommended by ddev-drupal-contrib) and then document in the README.md how to setup a local environment for contribution/maintenance.
Optional. Commit the changes in the .ddev folder after this plugin installs. This saves other users from having to install this integration.
Other projects where .ddev has been committed (by Moshe - Maintainer of DDEV Drupal Contrib).
https://git.drupalcode.org/project/domain_perm/-/tree/2.0.x?ref_type=heads
Proposed resolution
- Commit the .ddev/ folder and config.yaml file, compatible with version 1.23.0 of DDEV.
- Since DDEV doesn't auto-install Drush anymore, add
drush/drushto dev dependencies of the composer.json for standard cli tooling access. Note this module currently doesn't have any custom Drush commands, but it helps to have a fully functional DDEV local environment including drush, and it seems this is currently the only way. - Add CONTRIBUTING.md to document how to use DDEV Drupal Contrib and keep our dependencies up-to-date.
Issue fork views_bulk_operations-3532385
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
joelpittetNeed a tester to see if it will work before committing.
Comment #4
joelpittetMoving to the active branch and reroll
Comment #5
joelpittetCommitted to the 4.4.x branch