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.

Sign up for GitHub

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

Jump to bottom

Fix #3393 by making merge function more defensive. #3403

Merged
merged 1 commit into from
May 4, 2018
Merged

Fix #3393 by making merge function more defensive. #3403

merged 1 commit into from
May 4, 2018

Conversation

benjamn
Copy link
Member

@benjamn benjamn commented May 4, 2018 •
edited
Loading

Thanks to @HoangPaul for reporting this problem in #3393.

@benjamn benjamn requested a review from jbaxleyiii May 4, 2018 18:26
@apollo-cla
Copy link

apollo-cla commented May 4, 2018 •
edited
Loading

Warnings
⚠️

There are library changes, but not tests. That's OK as long as you're refactoring existing code
Messages
📖

Please add your name and email to the AUTHORS file (optional)

Generated by 🚫 dangerJS

@benjamn benjamn force-pushed the issue-3393-fix-graphql-anywhere-merge branch from 69a8e08 to 4fe42d3 Compare May 4, 2018 21:48
@benjamn benjamn merged commit 1677bb3 into master May 4, 2018
@benjamn benjamn mentioned this pull request Jun 6, 2018
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@jbaxleyiii jbaxleyiii Awaiting requested review from jbaxleyiii

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@benjamn @apollo-cla