Skip to content

Latest commit

 

History

History
62 lines (43 loc) · 1.92 KB

CONTRIBUTING.md

File metadata and controls

62 lines (43 loc) · 1.92 KB

How to Contribute

Finding things to contribute to

Please use the Issue Tracker to discuss potential improvements you want to make before sending a Pull Request. The roadmap is probably the best place to find areas where help would most be appreciated.

The Issue Tracker may contain items labelled help wanted or good first issue from time to time.

Pull Requests

Pull Requests are used for contributions. Code must be well-tested and not decrease the test coverage significantly.

Use a separate branch (not master)

Please commit changes to a separate branch in your fork so that we can work together making changes to it before it is ready to be merged. Name your branch something like <username>/feature.

Once you are ready, you can create a Pull Request for it to be merged into the master branch in this repo.

Testing

The following commands must pass for a Pull Request to be considered:

$ npm test
$ npm run lint

You can also check the test coverage by running:

$ npm run test:coverage

If you make changes to the docs

Use the following command to preview them:

$ npm run docsify

Contributor License Agreement

This project was created by a Google employee (although this is not an official Google project). Therefore, contributions to this project must be accompanied by a Contributor License Agreement. You (or your employer) retain the copyright to your contribution, this simply gives Google permission to use and redistribute your contributions as part of the project. Head over to https://cla.developers.google.com/ to see your current agreements on file or to sign a new one.

You generally only need to submit a CLA once, so if you've already submitted one (even if it was for a different project), you probably don't need to do it again.