|
1 | 1 | ## Contributing |
2 | 2 |
|
3 | | -[fork]: https://github.com/github/REPO/fork |
4 | | -[pr]: https://github.com/github/REPO/compare |
5 | | -[style]: https://github.com/styleguide/ruby |
6 | | -[code-of-conduct]: CODE_OF_CONDUCT.md |
7 | | - |
8 | 3 | Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great. |
9 | 4 |
|
10 | | -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](LICENSE.md). |
| 5 | +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. |
11 | 6 |
|
12 | | -Please note that this project is released with a [Contributor Code of Conduct][code-of-conduct]. By participating in this project you agree to abide by its terms. |
| 7 | +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. |
13 | 8 |
|
14 | 9 | ## Submitting a pull request |
15 | 10 |
|
16 | | -0. [Fork][fork] and clone the repository |
| 11 | +0. Fork and clone the repository |
17 | 12 | 0. Configure and install the dependencies: `script/bootstrap` |
18 | | -0. Make sure the tests pass on your machine: `rake` |
| 13 | +0. Make sure the tests pass on your machine: `script/cibuild` |
19 | 14 | 0. Create a new branch: `git checkout -b my-branch-name` |
20 | 15 | 0. Make your change, add tests, and make sure the tests still pass |
21 | | -0. Push to your fork and [submit a pull request][pr] |
| 16 | +0. Push to your fork and submit a pull request |
22 | 17 | 0. Pat your self on the back and wait for your pull request to be reviewed and merged. |
23 | 18 |
|
24 | 19 | Here are a few things you can do that will increase the likelihood of your pull request being accepted: |
25 | 20 |
|
26 | | -- Follow the [style guide][style]. |
| 21 | +- Follow standards for style and code quality |
27 | 22 | - Write tests. |
28 | 23 | - 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. |
29 | 24 | - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). |
|
0 commit comments