Skip to content

Latest commit

 

History

History
111 lines (76 loc) · 4.72 KB

CONTRIBUTING.md

File metadata and controls

111 lines (76 loc) · 4.72 KB
Raw

Contributing to graphql-js

We want to make contributing to this project as easy and transparent as possible. Hopefully this document makes the process for contributing clear and answers any questions you may have. If not, feel free to open an Issue.

Issues

We use GitHub issues to track public bugs and requests. Please ensure your bug description is clear and has sufficient instructions to be able to reproduce the issue. The best way is to provide a reduced test case on jsFiddle or jsBin.

Pull Requests

All active development of graphql-js happens on GitHub. We actively welcome your pull requests.

Considered Changes

Since graphql-js is a reference implementation of the GraphQL spec, only changes which comply with this spec will be considered. If you have a change in mind which requires a change to the spec, please first open an issue against the spec.

GraphQL Specification Membership Agreement

This repository is managed by EasyCLA. Project participants must sign the free GraphQL Specification Membership agreement before making a contribution. You only need to do this one time, and it can be signed by individual contributors or their employers.

To initiate the signature process please open a PR against this repo. The EasyCLA bot will block the merge if we still need a membership agreement from you.

You can find detailed information here. If you have issues, please email operations@graphql.org.

If your company benefits from GraphQL and you would like to provide essential financial support for the systems and people that power our community, please also consider membership in the GraphQL Foundation.

Getting Started

  1. Fork this repo by using the "Fork" button in the upper-right

  2. Check out your fork

    git clone git@github.com:your_name_here/graphql-js.git

  3. Install or Update all dependencies

    npm install

  4. Get coding! If you've added code, add tests. If you've changed APIs, update any relevant documentation or tests. Ensure your work is committed within a feature branch.

  5. Ensure all tests pass

    npm test

Coding Style

This project uses Prettier for standard formatting. To ensure your pull request matches the style guides, run npm run prettier.

  • 2 spaces for indentation (no tabs)
  • 80 character line length strongly preferred.
  • Prefer ' over "
  • ES6 syntax when possible. However do not rely on ES6-specific functions to be available.
  • Use TypeScript.
  • Use semicolons;
  • Trailing commas,
  • Avd abbr wrds.

Review Process

  • Pull requests are required to pass all tests and checks before they can be merged.
  • Pull requests should be reviewed by at least two members of the @graphql/graphql-js-reviewers team before they can be merged; ideally reviewers affiliated with different organizations
  • If a reviewer hasn't responded in 48 hours, feel free to ping them @graphql/graphql-js-reviewers.

Merge Process

Once a pull request has been approved by 2 reviewers from @graphql/graphql-js-reviewers team, we must wait 2 weeks before merging the pull request, this allows for other reviewers to give feedback without rushing any merges. Pull request can be merged by a member of the @graphql/graphql-js-reviewers team.

Release on NPM

Only core contributors may release to NPM.

To release a new version on NPM, first ensure all tests pass with npm test, then use npm version patch|minor|major in order to increment the version in package.json and tag and commit a release. Then git push && git push --tags to sync this change with source control. Then npm publish npmDist to actually publish the release to NPM. Once published, add release notes. Use semver to determine which version part to increment.

Example for a patch release:

npm test
npm version patch
git push --follow-tags
npm publish npmDist

License

By contributing to graphql-js, you agree that your contributions will be licensed under its MIT license.