-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix docker-compose options for the phpunit and composer environments #50406
Conversation
! isTTY ? '--no-TTY' : '', | ||
'-w', | ||
envCwd, | ||
useRun ? '--rm' : '', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested that empty string is acceptable when running exec (npx wp-env run cli ls
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does what it says on the tin
Size Change: 0 B Total Size: 1.37 MB ℹ️ View Unchanged
|
closing in favor of #50408 |
What?
This is kind of a partial revert of #50007 -- it restores the previous "docker-compose run" behavior for the phpunit and composer environments, which are not long-running envs.
This also fixes the root path of the composer environment -- the root cwd was changed in #49908 to the WordPress root which is different from what composer uses.
Why?
It's not possible to use these environments correctly on trunk.
How?
See above
Testing Instructions
local testing / tbd