-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
feat(docs): add to readme a link to contributing #239
Conversation
@Valorize Thanks 👍 have tweaked and will merge. In future, I'd advise that you create a branch for each pull request - pulling from your Also have a look at the commit naming in contributing.md :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks!
@calebmer Just wanted to check you're okay with this change. |
When I run the tests, should all tests pass in the moment (commit: 7f1a21b)? Because two of 2 of 498 failed. |
|
As it happens that's exactly the same reason #212 is failing. @calebmer 🚨 I think we should change the ts-node dependency from @Valorize Try: |
What this failure looks like to me is a GraphQL version less then |
Yeah, anyway thanks so much for this change @Valorize 🎉 I can confirm that the failing tests are caused by a GraphQL-js version less then |
Cool with the latest npm update all tests went green. |
* Added link to contributing file * Move contributing paragraph to its own section
@benjie