diff options
| author | Rich Leland <rich.leland@messagesystems.com> | 2015-07-02 16:59:59 -0400 |
|---|---|---|
| committer | Rich Leland <rich.leland@messagesystems.com> | 2015-07-02 16:59:59 -0400 |
| commit | e8b02a0e4060e789aa907c5a498dd9a3f4b64f10 (patch) | |
| tree | 2a002f33084dd5a940f2608a3d93c2ad6707c394 | |
| parent | fe0732983c7735b653681d904c958285d0c88fb9 (diff) | |
| download | php-sparkpost-e8b02a0e4060e789aa907c5a498dd9a3f4b64f10.zip php-sparkpost-e8b02a0e4060e789aa907c5a498dd9a3f4b64f10.tar.gz php-sparkpost-e8b02a0e4060e789aa907c5a498dd9a3f4b64f10.tar.bz2 | |
removed copy/pasta
| -rw-r--r-- | README.md | 9 |
1 files changed, 4 insertions, 5 deletions
@@ -97,9 +97,8 @@ Once all the dependencies are installed, you can execute the unit tests using `v If you're interested in code coverage, you can add the `--coverage` flag for phpunit like so: ```phpunit --coverage-html test/output/report --bootstrap test/unit/bootstrap.php ./test/unit``` ### Contributing -1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug. There is a `Contributor Friendly`_ tag for issues that should be ideal for people who are not very familiar with the codebase yet. -2. If you feel uncomfortable or uncertain about an issue or your changes, feel free to email @sigmavirus24 and he will happily help you via email, Skype, remote pairing or whatever you are comfortable with. -3. Fork [the repository](http://github.com/SparkPost/php-sparkpost) on GitHub to start making your changes to the **master** branch (or branch off of it). -4. Write a test which shows that the bug was fixed or that the feature works as expected. -5. Send a pull request and bug the maintainer until it gets merged and published. :) Make sure to add yourself to [AUTHORS](https://github.com/SparkPost/php-sparkpost/blob/master/AUTHORS.md). +1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug. +2. Fork [the repository](http://github.com/SparkPost/php-sparkpost) on GitHub to start making your changes to the **master** branch (or branch off of it). +3. Write a test which shows that the bug was fixed or that the feature works as expected. +4. Send a pull request and bug the maintainer until it gets merged and published. :) Make sure to add yourself to [AUTHORS](https://github.com/SparkPost/php-sparkpost/blob/master/AUTHORS.md). |