Chronos encourages contributions to this product.
Chronos welcomes all pull requests.
- Fork the repo and create a working branch from
master
. - If you've added any code that requires testing, add tests.
- If you've changed APIs, update the
README.md
. - Check to ensure that all tests pass.
- Make sure code is formatted with
prettier
and follows the Airbnb React/JSX Style Guide. - Create a pull request to
master
.
Please do not hesitate to file issues. Chronos is based off of community feedback and is always looking for ways to get better. The team behind Chronos is interested to hear about your experience and how we can improve it.
Please do not hesitate to submit issues that promote bugs or offer ways to enhance to Chronos. When submitting issues, ensure your description is clear and has instructions to be able to reproduce the issue.
We use GitHub as a platform of communication between users and developers to promote transparency. We thrive off of the community support and feedback