Problem/Motivation

To make this module easier to maintain, I would like to make a few changes...

  1. Update our GitLab CI config (let's take advantage of the community's latest changes)
  2. Install ddev/ddev-drupal-contrib (Ddev is now Drupal's official development environment. Its ddev/ddev-drupal-contrib plugin makes developing/contributing to contrib modules a lot easier.)
  3. Make it easier to use Drush to set up (i.e.: site-install) a development environment. (in ddev/ddev-drupal-contrib you install development dependencies by adding them to the require-dev section in composer.json.)

Proposed resolution

  1. Update .gitlab-ci.yml. Note the latest version at time-of-writing is 1.15.0.
  2. Run the ddev/ddev-drupal-contrib setup in this repo and commit the scaffolding to make setup easier. Note the latest version at time-of-writing is ddev/ddev-drupal-contrib 1.1.5.
  3. Add "require-dev": {"drush/drush": "*"} to composer.json. This will allow any version of drush that supports whichever version of core a user happens to be testing the feedback module with.

Remaining tasks

  1. Merge request - merge request !2 created by @mparker17 in #2
  2. Commit - merged in #4
  3. Release

User interface changes

None.

API changes

None.

Data model changes

None.

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

mparker17 created an issue. See original summary.

mparker17’s picture

Issue summary: View changes

  • mparker17 committed 503e5644 on 2.0.x
    feat: #3587146 Make maintenance easier: ddev-drupal-contrib, drush
    
    By:...
mparker17’s picture

Issue summary: View changes
Status: Active » Fixed

Merged. I'll update this issue when the change is released.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

mparker17’s picture

Issue summary: View changes

Status: Fixed » Closed (fixed)

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