Alain Schlesser
Alain Schlesser
This is something we have been discussing internally. There are still some details to figure out. I'll write up an issue with the current status and link it here. Related:...
> Note that while the proposed solution in this issue (shipping the phar in a composer package) would fix dependency conflicts during installation, it would not fix the conflicts during...
@ju1ius here's the issue with the discussion topics I mentioned: https://github.com/wp-cli/wp-cli/issues/5920 I'd love to get your insights on this.
I changed the folder where PIDs are stored and added that location to `.gitignore`: `tests/utils/pids`
@swissspidy This does not seem to take into account the efforts in other parts where we want to remove OS-specific solutions and conventions. The `/etc/` folder will not exist on...
I consider this a bug. When I run a command remotely, I expect it to exhibit the exact same behavior as if I would run it locally (minus whatever restrictions...
@copilot use `static function` for closures when no `$this` instance context is used.
Isn't this what the uppercase letter shows?
@swissspidy When you run anything with `wp ...`, it will use the Phar (and hence use the Phar's autoloader), and then the `wp-cli.yml` file will point it to the command...
Not sure I understand the problem here correctly. - what workflow is currently failing? - did you try switching from `wp` to `vendor/bin/wp` without deleting the `wp-cli.yml` file?