Contents

# Contributing

We love pull requests. Here's a quick guide:

1. Fork the repo.

2. Create your feature branch (`git checkout -b my-new-feature`)

3. Run the tests. We only take pull requests with passing tests, and it's great
to know that you have a clean slate: `bundle && rake`

4. Add a test for your change. Only refactoring and documentation changes
require no new tests. If you are adding functionality or fixing a bug, we need
a test!

5. Make the test pass.

6. Update [CHANGELOG.md](https://github.com/Helabs/jumpup-heroku/blob/master/CHANGELOG.md) with a brief description of your changes under the `unreleased` heading.

7. Commit your changes (`git commit -am 'Added some feature'`)

8. Push to the branch (`git push origin my-new-feature`)

9. Create new Pull Request

At this point you're waiting on us. We like to at least comment on, if not
accept, 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 is to follow the practices described on [Ruby style guide](https://github.com/bbatsov/ruby-style-guide), [Rails style guide](https://github.com/bbatsov/rails-style-guide) and [Better Specs](http://betterspecs.org/).

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
jumpup-heroku-0.0.6	CONTRIBUTING.md
jumpup-heroku-0.0.5	CONTRIBUTING.md
jumpup-heroku-0.0.4	CONTRIBUTING.md