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

Swapping to deeply nested merge rather than top-level. #2

Merged
merged 2 commits into from
Jan 4, 2017

Conversation

bzabos
Copy link
Contributor

@bzabos bzabos commented Dec 29, 2016

@alexlafroscia — This was more useful for me, let me know if this was intended behaviour.

@alexlafroscia
Copy link
Owner

Hey @bzabos -- I think that probably was the desired behavior. Could you add a test case that fails under the existing setup but passes after your change, so I can better understand the difference? Thanks!

@bzabos
Copy link
Contributor Author

bzabos commented Jan 4, 2017

@alexlafroscia — Sorry for delay; this has been added!

@alexlafroscia alexlafroscia merged commit 2e478c6 into alexlafroscia:master Jan 4, 2017
@alexlafroscia
Copy link
Owner

Great, thanks @bzabos!

@alexlafroscia
Copy link
Owner

Released 1.0.3 with your changes

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.

2 participants