Merged
Conversation
Member
|
@mjmahone Is this commit attributed to a different email address or similar that EasyCLA isn't correctly linking to you? |
Contributor
Author
|
Yes sorry I just need to re-upload the RFC. You got it exactly right: I was on a new email that wasn’t associated with GitHub. |
mjmahone
force-pushed
the
rfc-fragment-args
branch
from
4f277c1 to
2c83ac7
Compare
Member
|
The policy is to generally just merge RFCs without much oversight; so I'm going to do so. Thanks Matt! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Moving the RFC doc from graphql/graphql-spec#865 to the graphql-wg RFCs directory.
The original PR was created before graphql-wg had RFCs. This will make the spec PR cleaner.