Our team uses Drush frequently during the entire development workflow for doing things like grabbing database dumps of sites and running commands – drush make, registry rebuild, custom company-specific ones, etc. – and in the past everyone would have to manually download or copy them to their .drush.
Now, we version the .drush directory, so when a new developer onboards, they can just checkout the .drush directory from version control.
This is incredibly useful for
- Sharing dynamic drush aliases across team members
- Enforcing drush policy
- Sharing commands, like registry-rebuild, and others
You can build a very powerful devops toolkit across all team members since everyone will have the same Drush setup!