Contributing to ReactiveShipping

We love receiving pull requests! Anything from new carriers to documentation fixes.

Also, we are looking for maintainers for the current version of ReactiveShipping 2.0.

Standards

  • PR should explain what the feature does, and why the change exists.
  • PR should include any carrier specific documentation explaining how it works.
  • Code must be tested, including both unit and remote tests where applicable.
  • Be consistent. Write clean code that follows Ruby community standards.
  • Code should be generic and reusable.

If you're stuck, ask questions!

How to contribute

  1. Fork it ( https://github.com/realsubpop/reactive_shipping/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request