Drush Help
Categories
Component ID
Component name
Component type
Maintenance status
Development status
Component security advisory coverage
Downloads
Component created
Component changed
Component body
To see the drush commands help you need to use drush help COMMAND_NAME from the command line, but if you want to see this information in Drupal you'll can't do it.
This module improves the module help page showing information about the module drush commands.
The drush command help section only will be added if the module for which you are viewing the help have drush commands defined.
Issues
As with all contributed modules, when considering submitting an issue:
- Read the documentation (two or three times is better). Don't forget the home page.
- Review the existing issues list. (Don't forget to select "<- Any ->" for the "Status" field.)
- Gather all the appropriate information. This may include (but is not limited to):
- Drupal version.
- Browser type and version.
- Database type and version.
- Error messages, if any.
- Module settings.
- Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
- If you go to provide a patch use the following naming convention:
[drush_help]-[short-description]-[issue-number]-[comment-number]-[drupal-version].patch
And please don't forget to use the Issue Summary Template to report an issue, if you need help to understand how the issue queue works, see the Getting Started in the Issue Queue video.
Development version status
The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get by us. Your help on testing this code is greatly appreciated. The translation templates may not always be up-to-date in the dev releases.