To solve the bug exit equals 0 when some commands become failed
What problem is this solving?
Commands like publish, uninstall, unlink when they fail the CLI doesn't return exit code 1, If someone use this in a CI/CD, the pipeline will run "normally" and won't fail with CLI vtex
How should this be manually tested?
Force some error like trying to publish a version that already exists:
vtex publish
The CLI must exit with status code 1 instead 0
Screenshots or example usage
Types of changes
[x] Refactor (non-breaking change that only makes the code better)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.
ayelsew
commented
6 months ago
What is the purpose of this pull request?
To solve the bug exit equals 0 when some commands become failed
What problem is this solving?
Commands like publish, uninstall, unlink when they fail the CLI doesn't return exit code 1, If someone use this in a CI/CD, the pipeline will run "normally" and won't fail with CLI vtex
How should this be manually tested?
Force some error like trying to publish a version that already exists:
vtex publishThe CLI must exit with status code 1 instead 0Screenshots or example usage
Types of changes
Chores checklist
CHANGELOG.md