Problem/Motivation

Adding a .ddev folder to a contrib module exists purely for maintainers and contributors to have a way to easily spin up a local standalone environment when cloning from the module repository directly. But presence of the .ddev folder in package builds intended for real Drupal websites can be confusing and can lead to accidental ddev environment spin ups of the module instead of the website project, which is not recommended and can have unintended consequences.

Proposed resolution

Exclude .ddev folder from composer packages using the gitattributes export-ignore approach outlined here:

https://stackoverflow.com/a/17069547/413538

Alternatively, have Drupal.org packaging maintainers to exclude .ddev folders for all contrib project builds.

Issue fork piwik_pro-3505055

Command icon 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

heikkiy created an issue. See original summary.

hartsak’s picture

Version: 1.2.x-dev » 1.3.x-dev

  • hartsak committed 7c40b2b0 on 1.3.x authored by heikkiy
    Issue #3505055 by heikkiy, hartsak: Ignore .ddev folder on composer...
hartsak’s picture

Status: Active » Fixed

Ok, this looks good to me!
Reviewed and fixed at the same time. Thanks HeikkiY!

  • hartsak committed 81c51283 on 1.2.x
    Issue #3505055 by hartsak, heikkiy: Ignore .ddev folder on composer...
hartsak’s picture

Backported to 1.2.x also.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.