CONTRIBUTING.md

Contributing

1. Fork it
2. Install dependencies (yarn install)
3. Create your feature branch (git checkout -b my-new-feature)
4. Commit your changes (git commit -am 'feat: added some feature')
5. Test your changes (yarn test)
6. Push to the branch (git push origin my-new-feature)
7. Create new Pull Request

Testing

We use Jest to write tests. Run our test suite with this command:

yarn test

Code Style

We use Prettier and tslint to maintain code style and best practices. Please make sure your PR adheres to the guides by running:

yarn format

and

yarn lint

Commitlint

commitlint checks if your commit messages meet the conventional commit format.

In general the pattern mostly looks like this:

type(scope?): subject  #scope is optional; multiple scopes are supported (current delimiter options: "/", "\" and ",")

Real world examples can look like this:

chore: run tests on travis ci

fix(server): send cors headers

feat(blog): add comment section

Common types according to commitlint-config-conventional (based on the Angular convention) can be:

• build
• ci
• chore
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test