Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix guard notification settings #218

Closed
wants to merge 1 commit into from
Closed

Fix guard notification settings #218

wants to merge 1 commit into from

Conversation

amiel
Copy link

@amiel amiel commented Nov 21, 2013

::Bundler.with_clean_env is clobbering the GUARD_NOTIFY and GUARD_NOTIFIERS
environment variables needed for notification settings. This change resets
guard related environment variables that have been reset by Bundler.

I think this addresses the same issue as #217, although #217 also contains a bunch of refactors.

::Bundler.with_clean_env is clobbering the GUARD_NOTIFY and GUARD_NOTIFIERS
environment variables needed for notification settings. This change resets
guard related environment variables that have been reset by Bundler.
@coveralls
Copy link

Coverage Status

Coverage increased (+6.83%) when pulling 806f9cc on carnesmedia:fix-guard-notifications into 8574398 on guard:master.

it "does not clobber GUARD ENV vars" do
ENV['GUARD_NOTIFY'] = 'true'
Kernel.should_receive(:system) do
expect(ENV['GUARD_NOTIFY']).to eq 'true'
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm all ears if you have a suggestion for another way to test the state of ENV vars during the Kernel.system call. I couldn't think of another way to do this...

@907th
Copy link
Contributor

907th commented Nov 21, 2013

Good! Works for me. That can be considered as a solution until #217 will be accepted

@thibaudgg
Copy link
Member

Yeah I think that #217 is a better of fixing it. We'll merge it today hopefully.

@thibaudgg
Copy link
Member

Fixed by #217

@thibaudgg thibaudgg closed this Dec 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants