Skip to content

Latest commit

 

History

History
38 lines (26 loc) · 1.91 KB

CONTRIBUTING.md

File metadata and controls

38 lines (26 loc) · 1.91 KB
Raw

Questions

If you have issues with the APIs or have a question about the Watson services, see Stack Overflow.

Code

  • Commits should follow the Angular commit message guidelines. This is because our release tool uses this format for determining release versions and generating changelogs. To make this easier, we recommend using the Commitizen CLI with the cz-conventional-changelog adapter.

Issues

If you encounter an issue with the Ruby library, you are welcome to submit a bug report. Before that, please search for similar issues. It's possible somebody has already encountered this issue.

Pull Requests

If you want to contribute to the repository, follow these steps:

  1. Fork the repo.
  2. Install bundler if needed: gem install bundler
  3. Install the dependencies: bundle install
  4. Make code changes.
  5. Add a test for your changes. Only refactoring and documentation changes require no new tests.
  6. Make the test pass, test your code changes: bundle exec rake.
  7. Commit your changes.
  8. Push to your fork and submit a pull request.
  9. Travis-CI and AppVeyor will run the tests for all services once your changes are merged.

Tests

Ideally, we'd like to see both unit and integration tests on each method. (Unit tests do not actually connect to the Watson service, integration tests do.)

Out of the box, rake runs integration and unit tests. Put the corresponding credentials in a .env file in the root directory for the integration tests to work as intended. To just run unit or integration tests, run rake test:unit or rake test:integration

For the integration tests, tests will only be run for services that have credentials defined in a .env file.