Fix drush wrapper #355
Merged
Fix drush wrapper #355
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joecorall
force-pushed
the
fix-drush-wrapper
branch
from
882fd7b
to
8ae865f
Compare
nigelgbanks
approved these changes
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to composer/composer#12164 (specifically https://github.com/composer/composer/pull/12176/files)
/var/www/drupal/vendor/bin/drushis a shell script in drush 13.3.1+. Since we're setting the memory limit when calling drush, we can just call drush.php instead.This should be OK per moshe (drush creator/maintainer) in Drupal slack when discussing a similar issue someone was having
Also while testing this locally added the one missing documentation issue for Mac OS to the README, so we can close #342