exp/CONTRIBUTING.md

31 lines
1.6 KiB
Markdown
Raw Normal View History

2019-02-15 14:29:39 +00:00
## Contributing
Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
2019-02-15 18:42:08 +00:00
Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the project's open source license.
2019-02-15 14:29:39 +00:00
2019-02-15 18:42:08 +00:00
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
2019-02-15 14:29:39 +00:00
## Submitting a pull request
2019-02-15 18:42:08 +00:00
0. Fork and clone the repository
2019-02-15 14:29:39 +00:00
0. Configure and install the dependencies: `script/bootstrap`
2019-02-15 18:42:08 +00:00
0. Make sure the tests pass on your machine: `script/cibuild`
2019-02-15 14:29:39 +00:00
0. Create a new branch: `git checkout -b my-branch-name`
0. Make your change, add tests, and make sure the tests still pass
2019-02-15 18:42:08 +00:00
0. Push to your fork and submit a pull request
2019-02-15 14:29:39 +00:00
0. Pat your self on the back and wait for your pull request to be reviewed and merged.
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
2019-02-15 18:42:08 +00:00
- Follow standards for style and code quality
2019-02-15 14:29:39 +00:00
- Write tests.
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
## Resources
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
- [GitHub Help](https://help.github.com)