Refactor how status works - keep "set -e" #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I like this! I prefer to keep |
mislav
added a commit
that referenced
this pull request
Sep 29, 2015
Refactor how status works - keep "set -e" Closes #17
|
Awesome, thanks for merging! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @mislav - I personally find the way the status check is implemented in the script a tad confusing, so I'm offering two alternate implementations, one that keeps
"set -e"(this one) and another one that removes it (see #17)This PR keeps
"set -e", but combines the two pipelines into a single one to avoid the need for the superfluousSTATUSvariable.