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.

Sign up for GitHub

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

Jump to bottom

Define an exit code policy #170

Closed
epage opened this issue Nov 12, 2020 · 1 comment · Fixed by #173
Closed

Define an exit code policy #170

epage opened this issue Nov 12, 2020 · 1 comment · Fixed by #173
Labels
bug Not as expected

Comments

@epage
Copy link
Collaborator

epage commented Nov 12, 2020

See https://docs.rs/exit-code/1.0.0/exit_code/

Including broken pipe

Codes of interest

  • USAGE_ERROR
  • CONFIG_ERROR
  • FAILURE for runtime errors?
  • DATA_ERROR for typos?
@epage epage added the bug Not as expected label Nov 12, 2020
@epage
Copy link
Collaborator Author

epage commented Nov 15, 2020

Broken pipe is split out into #172

epage pushed a commit to epage/typos that referenced this issue Nov 15, 2020
fix(cli): Define an error code policy
2bb2830 
The main goal is to make spelling errors differentiated from other
errors.

Fixes crate-ci#170
@epage epage mentioned this issue Nov 15, 2020
Merged
epage pushed a commit to epage/typos that referenced this issue Nov 15, 2020
fix(cli): Define an error code policy
4ddbdcf 
The main goal is to make spelling errors differentiated from other
errors.

Fixes crate-ci#170
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Not as expected
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(cli): Define an error code policy epage/typos
1 participant
@epage