You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The status code returned by wp should be properly set, this helps with command chaining or handling failures.
$ wp ajsodjasiodjsaiod
Error: 'ajsodjasiodjsaiod' is not a registered wp command. See 'wp help' for available commands.
$ echo $?
1
$ vip @app.env wp ajsodjasiodjsaiod
Error: 'ajsodjasiodjsaiod' is not a registered wp command. See 'wp help' for available commands.
$ echo $?
1
Actual Behavior
$ wp ajsodjasiodjsaiod
Error: 'ajsodjasiodjsaiod' is not a registered wp command. See 'wp help' for available commands.
$ echo $?
1
$ vip @app.env wp ajsodjasiodjsaiod
Error: 'ajsodjasiodjsaiod' is not a registered wp command. See 'wp help' for available commands.
$ echo $?
0
Steps to Reproduce the Problem
Step 1: Run a vip @app.env wp command that throws an error or otherwise returns an error status code through standard WP CLI.
Step 2: Check the returned status code, and notice it is always "0".
The text was updated successfully, but these errors were encountered:
This issue has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.
This is an automation to keep issues manageable and actionable and is not a comment on the quality of this issue nor on the work done so far. Closed issues are still valuable to the project and are available to be searched.
Expected/Desired Behavior
The status code returned by wp should be properly set, this helps with command chaining or handling failures.
Actual Behavior
Steps to Reproduce the Problem
vip @app.env wp
command that throws an error or otherwise returns an error status code through standard WP CLI.The text was updated successfully, but these errors were encountered: