Options when enabling modules via Drush

Created on 3 September 2014, about 10 years ago
Updated 15 February 2024, 9 months ago

Not sure if I'm just missing something somewhere... so I went for "Support Request".

When enabling a module via Drush, one of the prompts is to update dependencies via Composer Manager, which is great. It's nice to be able to do drush en module --yes and have all of that taken care of.

However, it appears that all dependencies are installed, including require-dev. Additionally, rather than downloading from source, it downloads via api.github.com. Of course, this is all fine and dandy in most cases.

Where I run into problems is when I'm testing a module on Travis CI. It doesn't take long to get rate limited by Github. What I'd like to be able to do is provide some sort of options to Composer Manager (whether via CLI on pm-enable or $conf) so that Composer Manager will pass the --no-dev, -n, and --prefer-source options. This way, instead of hitting Github's download API and getting rate limited, a simple clone can be done.

Of course, I could just be missing something that already exists or simply drawing a blank on a workaround.

💬 Support request
Status

Closed: outdated

Version

1.0

Component

Miscellaneous

Created by

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

No activities found.

Production build 0.71.5 2024