Provide a drush features:fork command

Created on 29 January 2024, 11 months ago

Problem/Motivation

I'd like to easily be able to "fork" a feature on a site by running a drush command that will do the following:

  • Prompt for a module name if not provided as an argument. Should the module be validated to be enabled currently? It doesn't make much sense to fork a feature that hasn't been enabled yet.
  • Performs a recursive copy of the feature module directory to the modules/custom directory (can be overridden by --destination option).
  • Should probably delete the config/install and config/optional directories? Or should we just keep them?
✨ Feature request
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States dave reid Nebraska USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024