Add the ability to initialize all guards at once and a --bare option to the init task #232
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
|
Awesome, very good work! We'll release that in Guard 1.1, thanks. |
thibaudgg
added a commit
that referenced
this pull request
Jan 28, 2012
Add the ability to initialize all guards at once and a --bare option to the init task
|
Woot, thanks a lot! |
|
You are all more than welcome, keep up the good work :) |
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.
Hello Guard core-devs,
Today I have spent some time implementing a feature-request I found on your issues-tracker.
As a consequence of the new features, Guard has changed a bit:
inittask defaults now to searching for installed guards and adding them to the new Guardfile.--bareor-boption for theinittask. This will just generate a Guard file with the default Guard template.inittask with the--bareoption will display an error and abort the Guard process if a Guardfile already exists (just like it used to do). This is not the case when invoking theinittask with or w/o a guard name; These will result in adding the same templates to theGuardfile.The new features has been documented, tested and added to the README file. I also made sure that all tests pass on travis-ci to make merging this feature easier.
Cheers