If there's no recommended release and only one available, we should just download that one rather than prompt.

This is currently the case with git_deploy.

CommentFileSizeAuthor
#1 dl_noprompt-1073476-1.patch1.59 KBmsonnabaum

Comments

msonnabaum’s picture

msonnabaum commented
StatusFileSize
new dl_noprompt-1073476-1.patch1.59 KB
greg.1.anderson’s picture

greg.1.anderson commented
Status: Active » Needs work

Originally it was by design that drush would not download non-recommended releases without prompting.

I'm not opposed to changing, I'm just saying. I feel kind of mixed about it. At a minimum, I think we should log a warning that the release is not recommended.

damien tournoud’s picture

damien tournoud commented

I am -1 about this change. Even when there are only one non-recommended version available, there are actually two choices: download or not.

msonnabaum’s picture

msonnabaum commented

I can see the argument for how it is now, but if nothing else it seems like we should maybe have an option to not prompt for non recommended releases.

The problem I see is that if I download a module with no recommended release, it has to be interactive. I can't just pass a -y to it. For those of us that know what we're doing when we download a dev-only module, it'd be nice for drush to not get in our way.

greg.1.anderson’s picture

greg.1.anderson commented

Actually, you can pass -y if there is only one option for drush_choice. With -y, drush_choice will pick the first release if there is only one option (plus cancel), or it will cancel if there are two options. You could also pass --choice=1 to always pick the newest release.

greg.1.anderson’s picture

greg.1.anderson commented
Version: » 8.x-6.x-dev
Status: Needs work » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.