Skip to content
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

Known errors should not be logged as crashes #45

Closed
Reinmar opened this issue Feb 13, 2017 · 1 comment · Fixed by #54
Closed

Known errors should not be logged as crashes #45

Reinmar opened this issue Feb 13, 2017 · 1 comment · Fixed by #54

Comments

@Reinmar
Copy link
Member

Reinmar commented Feb 13, 2017

image

I may be the author of this, but I was confused whether the tool failed gracefully or heavily. If we catch an issue, it shouldn't be that verbose. We just need the message to be logged.

@pomek
Copy link
Member

pomek commented Feb 13, 2017

After merging #44 we have 100% CC for commands, so we can improve it now. I will correct it.

@pomek pomek self-assigned this Feb 13, 2017
Reinmar added a commit that referenced this issue Aug 16, 2017
Feature: Introduced new commands and fixes bugs related to invalid displayed errors. Closes #2. Closes #45. Closes #49. Closes #52.

- New commands:
  * `checkout` – changes branches in repositories according to the configuration file (see #52),
  * `diff` – prints changes from all repositories (see #2),
  * `status` – prints a table which contains useful information about the status of repositories (see #2).
- Bug fixes:
  * known errors should not be logged as crashes (see #45),
  * fixed `Unhandled promise` error (see #49).
- Added support for aliases (`st` => `status`, `co` => `checkout`).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants