Skip to content

Commit

Permalink
Small Review Edits.
Browse files Browse the repository at this point in the history
  • Loading branch information
alexmoore authored Nov 9, 2016
1 parent 5f8a390 commit 1b4a2e3
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,16 +6,16 @@ This repo's maintainers are engineers at Basho and welcome your contribution to

**_IMPORTANT_**: This is an open source project licensed under the Apache 2.0 License. We encourage contributions to the project from the community. We ask that you keep in mind these considerations when planning your contribution.

* Whether your contribution is for a bug fix or a feature request, **create an [Issue](https://github.com/basho/riak-java-client/issues)** and let us know what you are thinking.
* Whether your contribution is for a bug fix or a feature request, **create an [issue](https://github.com/basho/riak-java-client/issues)** and let us know what you are thinking.
* **For bugs**, if you have already found a fix, feel free to submit a Pull Request referencing the Issue you created.
* **For feature requests**, we want to improve upon the library incrementally which means small changes at a time. In order ensure your PR can be reviewed in a timely manner, please keep PRs small, e.g. <10 files and <500 lines changed. If you think this is unrealistic, then mention that within the Issue and we can discuss it.
* For help on running Integration tests, please see [The README section on this subject](https://github.com/basho/riak-java-client#contributing).
* For help on running Integration tests, please see [the README section on this subject](https://github.com/basho/riak-java-client#contributing).

### Pull Request Process

Here’s how to get started:

* [Create an Issue](https://github.com/basho/riak-java-client/issues/new) that explains the bug or new feature.
* [Create an issue](https://github.com/basho/riak-java-client/issues/new) that explains the bug or new feature.
* Fork the appropriate sub-projects that are affected by your change.
* Create a topic branch for your change and checkout that branch.
`git checkout -b some-topic-branch`
Expand Down

0 comments on commit 1b4a2e3

Please sign in to comment.