Skip to content

Latest commit

 

History

History
38 lines (26 loc) · 2.18 KB

CONTRIBUTING.md

File metadata and controls

38 lines (26 loc) · 2.18 KB
Raw

Contributing to this project

Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Contribution Agreement

As a contributor, you represent that the code you submit is your original work or that of your employer (in which case you represent you have the right to bind your employer). By submitting code, you (and, if applicable, your employer) are licensing the submitted code to the open source community subject to the MIT license.

Submitting a pull request

  1. Fork and clone the repository
  2. Create a new branch: git checkout -b feature/my-new-feature-name
  3. Run npm install to make sure you've got the latest dependencies.
  4. Make your change
  5. Run the unit tests and make sure they pass and have 100% coverage. (npm test)
  6. Push to your fork and submit a pull request
  7. Pat your self on the back and wait for your pull request to be reviewed and merged.

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

  • Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
  • Make your commit message follow Conventional Commits.
  • In your pull request description, provide as much detail as possible. This context helps the reviewer to understand the motivation for and impact of the change.
  • Make sure that all the unit tests still pass. PRs with failing tests won't be merged.

Resources