indusbit-test/CONTRIBUTING.md

Test package for IndusBit

# Contributing

We love pull requests from everyone. By participating in this project, you
agree to abide by the [code of conduct].

[code of conduct]: https://github.com/indusbit/indusbit-test/blob/master/code_of_conduct.md

Fork, then clone the repo:

    git clone git@github.com:your-username/indusbit-test.git

Make your change.

Push to your fork and [submit a pull request][pr].

[pr]: https://github.com/indusbit/indusbit-test/compare/

At this point you're waiting on us. We like to at least comment on pull requests
within three business days (and, typically, one business day). We may suggest
some changes or improvements or alternatives.

Some things that will increase the chance that your pull request is accepted:

- Write a good commit message
- Make sure all the tests are passing

## Contributing Code

Checkout the latest master to make sure the feature hasn't been implemented or
the bug hasn't been fixed yet.

Check the issue tracker to make sure someone already hasn't requested it and/or
contributed to it.

1. Use the example project to test the module.
2. Delete the `postinstall` step from `package.json`. Remember to revert this
   change when commiting.
3. Edit example/reload.sh to configure your path.
4. Follow instructions to link your project with the iOS SDK, as given in the [README].
5. Run example/reload.sh every time you make a change to the module.

Make your change. Follow this [style guide][style].

Push to your fork. Write a [good commit message][commit]. Submit a pull request.

Others will give constructive feedback.
This is a time for discussion and improvements,
and making the necessary changes will be required before we can
merge the contribution.

[commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html "A short guide on how to write good commit messages"
[README]: README.md#linking-ios-sdk "Linking to the iOS SDK"
[style]: https://github.com/thoughtbot/guides/tree/master/style "Styleguides by Thoughtbot"