Please, follow the golden rule. Be respectful, even to those that are disrespectful.
I would love to hear your opinions, discuss potential improvements, architecture, theory, internal implementation, etc. Please, join or start a new conversation in our issue tracker.
We need your help with improving documentation to the project. This might be the easiest way for
you to contribute, because you don't even need to clone the repo but can edit or create new .md
files right from GitHub website as described here.
Before opening an issue, please:
- Search the issue tracker to make sure your issue hasn’t already been reported.
Before you submit a pull request from your forked repo, check that it meets these guidelines:
- If the pull request adds functionality, the docs should be updated as part of the same PR.
- Create a separate PR for each small feature or bug fix.
- Squash your commits into one for each PR.
- Run
npm test
to make sure that your code style is OK and there are no any regression bugs.
Our linter will catch most styling issues that may exist in your code. You can check the status
of your code styling by simply running: npm run lint
However, there are still some styles that the linter cannot pick up. If you are unsure about something, looking at Airbnb's Style Guide will guide you in the right direction.
By contributing to Champion Select, you agree that your contributions will be licensed under its MIT license.