Skip to content

halt(1) after 'elvis rock' invocation fails. #176

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
Nov 19, 2014
Merged

halt(1) after 'elvis rock' invocation fails. #176

merged 1 commit into from
Nov 19, 2014

Conversation

emauton
Copy link
Contributor

@emauton emauton commented Nov 19, 2014

This makes 'elvis rock' usable in e.g. continuous integration systems or other
automation relying on the usual shell return codes to detect failure.
Cf. #175

This change also:

  • fixes a couple of typos (unimplemened -> unimplemented, emtpy -> empty);
  • adds mocks for erlang_utils:erlang_halt around every invocation of main()
    that calls 'rocks';
  • standardizes use of meck:unload/1 throughout - some were in 'catch'
    expressions, some not; this doesn't appear to be necessary.

This makes 'elvis rock' usable in e.g. continuous integration systems or other
automation relying on the usual shell return codes to detect failure.
Cf. #175

This change also:
* fixes a couple of typos (unimplemened -> unimplemented, emtpy -> empty);
* adds mocks for erlang_utils:erlang_halt around every invocation of main()
  that calls 'rocks';
* standardizes use of meck:unload/1 throughout - some were in 'catch'
  expressions, some not; this doesn't appear to be necessary.
elbrujohalcon pushed a commit that referenced this pull request Nov 19, 2014
halt(1) after 'elvis rock' invocation fails.
@elbrujohalcon elbrujohalcon merged commit 29a0790 into inaka:master Nov 19, 2014
@emauton emauton deleted the emauton.175.return.shell.failure branch November 19, 2014 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants