run_on_start option is no longer dependent on the run_on_all option. #19
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
added 2 commits
August 14, 2012 11:10
run_on_start option is no longer dependent on the run_on_all option.
|
I also fixed a name clashing issue which looks like it has reappeared. Guard::Rake was defined as both a class and a module. |
rubyist
pushed a commit
that referenced
this pull request
Aug 15, 2012
run_on_start option is no longer dependent on the run_on_all option.
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.
The run_on_start option doesn't currently work unless run_on_all is also set to true.
This fix decouples the two options so you can set them independently.