We are open to, and grateful for, any contributions made by the community. Thanks for your interest in contributing! Here's a few things to keep in mind when contributing to this project:
Before opening an issue, please search the issue tracker to make sure your issue hasn’t already been reported.
We use the issue tracker to keep track of bugs and improvements to es2015-i18n-tag itself, its examples, and the documentation. We encourage you to open issues to discuss improvements, architecture, internal implementation, etc. If a topic has been discussed before, we will ask you to join the previous discussion.
For support or usage questions, please search and ask on StackOverflow with a es2015-i18n-tag tag. We ask you to do this because StackOverflow has a much better job at keeping popular questions visible. Unfortunately good answers get lost and outdated on GitHub.
For non-trivial changes, please open an issue with a proposal for a new feature or refactoring before starting on the work. We don’t want you to waste your efforts on a pull request that we won’t want to accept.
Please try to keep your pull request focused in scope and avoid including unrelated commits.
After you have submitted your pull request, we’ll try to get back to you as soon as possible. We may suggest some changes or improvements.
This project uses ghooks to run commit-msg and pre-commit hooks.
We use semantic-release to manage releases. This means we have a convention for our commit messages. Please follow our commit message convention even if you're making a small change. This repository follows the How to Write an Open Source JavaScript Library series on egghead.io (by yours truly). See this lesson and this repo to learn more about the commit message conventions.