Skip to content
This repository has been archived by the owner on Apr 27, 2020. It is now read-only.

Adapts guard-unicorn plugin to the new Guard API #14

Merged
merged 1 commit into from Nov 11, 2014

Conversation

zukunftsalick
Copy link
Contributor

Silences the warnings we get from Guard

more info on https://github.com/guard/guard/wiki/Upgrading-to-Guard-2.0#changes-in-guardguard

@andreimaxim
Copy link
Owner

Can you also fix the initialize method so we'll have just one commit?

@zukunftsalick
Copy link
Contributor Author

Sure. I'll fix it after lunch :)
On Nov 11, 2014 1:05 PM, "Andrei Maxim" notifications@github.com wrote:

Can you also fix the initialize method so we'll have just one commit?


Reply to this email directly or view it on GitHub
#14 (comment)
.

@zukunftsalick
Copy link
Contributor Author

I've just squashed the commits to one commit

@andreimaxim
Copy link
Owner

Awesome, thank you very much! I'm merging it now and I'll release a new gem version later today.

andreimaxim added a commit that referenced this pull request Nov 11, 2014
Adapts guard-unicorn plugin to the new Guard API
@andreimaxim andreimaxim merged commit ca5177d into andreimaxim:master Nov 11, 2014
@zukunftsalick
Copy link
Contributor Author

@andreimaxim Hi, mind making a new gem release? I would like to avoid having my Gemfile pointing to commit hashes :)

@andreimaxim
Copy link
Owner

Sorry, totally forgot about this. v0.1.3 is now available on Rubygems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants