Skip to content

fix: migrate command failure should be handled correctly #4807

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

Merged
merged 1 commit into from
Jul 5, 2019

Conversation

rosen-vladimirov
Copy link
Contributor

In case migrate command fails to migrate the project, currently it shows some generic message without saying what is the actual error. Also the command exits with code 0, which is indication it had succeeded.
Fix this by failing with more descriptive error message and exit code that is not 0.

PR Checklist

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

In case migrate command fails to migrate the project, currently it shows some generic message without saying what is the actual error. Also the command exits with code 0, which is indication it had succeeded.
Fix this by failing with more descriptive error message and exit code that is not 0.
@rosen-vladimirov rosen-vladimirov self-assigned this Jul 5, 2019
@cla-bot cla-bot bot added the cla: yes label Jul 5, 2019
@rosen-vladimirov rosen-vladimirov merged commit 10ce323 into release Jul 5, 2019
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/fix-migrate branch July 5, 2019 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants