-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
[Status] KeepPrevent the "stale" workflow from auto-closingPrevent the "stale" workflow from auto-closing
Description
Expected/Desired Behavior
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 wpcommand 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".
Metadata
Metadata
Assignees
Labels
[Status] KeepPrevent the "stale" workflow from auto-closingPrevent the "stale" workflow from auto-closing