fotingo should exit with a non zero code when there is an error #622

tagoro9 · 2020-09-04T18:04:57Z

Right now it is exiting with a 0 exit code and that makes it hard to use inside CI

Fixes #622

## [2.2.3](v2.2.2...v2.2.3) (2020-09-04) ### Bug Fixes * exit with non-zero code when there are errors ([04e73e7](04e73e7)), closes [#622](#622) * **ui:** exit ui passing errors when there are any ([1c7f84f](1c7f84f))

github-actions · 2020-09-04T22:19:03Z

🎉 This issue has been resolved in version 2.2.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

tagoro9 added the Type: Bug label Sep 4, 2020

tagoro9 added a commit that referenced this issue Sep 4, 2020

fix: exit with non-zero code when there are errors

3e2156d

Fixes #622

tagoro9 mentioned this issue Sep 4, 2020

fix: exit with non-zero code when there are errors #623

Merged

tagoro9 closed this as completed in #623 Sep 4, 2020

tagoro9 added a commit that referenced this issue Sep 4, 2020

fix: exit with non-zero code when there are errors

04e73e7

Fixes #622

github-actions bot added the released label Sep 4, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fotingo should exit with a non zero code when there is an error #622

fotingo should exit with a non zero code when there is an error #622

tagoro9 commented Sep 4, 2020

github-actions bot commented Sep 4, 2020

fotingo should exit with a non zero code when there is an error #622

fotingo should exit with a non zero code when there is an error #622

Comments

tagoro9 commented Sep 4, 2020

github-actions bot commented Sep 4, 2020