We want this community to be friendly and respectful to each other. Please read the full text so that you can understand what actions will and will not be tolerated.
The core team works directly on GitHub and all work is public.
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub
Before submitting a pull request, please make sure the following is done:
- Fork the repo and create your branch from
master
(a guide on how to fork a repository). - We have a commit message convention:
fix
- bug fixesfeature
- new features, e.g. add GrouppeList componentdocs
- code/structure refactor, e.g. new structure folder for componentsrefactor
- changes into documentation, e.g. add usage example for Buttonchore
- tooling changes, e.g. change circle ci config
- Always make sure that your code passes
eslint
before opening a PR. - If you've changed APIs, update the documentation.
- Make sure to provide an example usage (check how others do it).
Just run yarn example:web
.
After each change you have to build code using yarn build:babel
.
The best way to get your bug fixed is to provide a reduced test case. Please provide a public repository with a runnable example if possible.
- Callstack Open Source Slack - #react-theme-provider
We use Prettier with ESLint integration.
By contributing to @callstack/react-theme-provider
, you agree that your contributions will be licensed under its MIT license.