0.8.5 Broken: Fix guard init path to Guardfile template
#168
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
|
Damn, not again! This was exactly the reason why I added specs to it, but I didn't verify the existence of the template. I added that missing spec and hope I never have to handle that again :P Thanks a lot for the pull request, I merged it into the |
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.
Between 0.8.4 and 0.8.5, the file that calls the
guard inittask changed, but the path to the template Guardfile was not adjusted accordingly. This results in an error when doingguard initusing version 0.8.5 of this gem.This pull request makes the small tweak necessary to point to the correct path of the Guardfile.