This repository is set up to work under the traditional fork + Pull Request model.
Quality is validated in pull requests using travis-ci.com using the configuration that you can see in the Travis YAML.
The script
phase of the Travis lifecycle will run the linter and tests. The after_script
phase sends to coverage results to coveralls.io.
Pull requests with failing builds will not be merged, and coverage is expected to be above 80%.
Releases are responsability of the maintainers. When releasing maintainers should:
- Make sure
CHANGELOG.md
is updated - Create a git tag
- Create a new npm version
- Publish to npm
- Push the branch