Contents

## Contributing

0. Raise an issue in this project outlining the change you'd like to make. You'll need the `issue_number`
1. Fork this project into your own Github account
2. Create your feature branch (`git checkout -b {issue_number}_my-new-feature`)
4. Push to the branch (`git push -u origin {issue_number}_my-new-feature`)
5. Write RSpec tests to formalise the outcomes of your change
6. Write the code to implement the changes, ensuring that the tests eventually pass
7. Commit your changes (`git commit -am '{issue_number} Added some feature'`)
8. Push to the branch (`git push -u origin my-new-feature`)
9. Create a new Pull Request using Github's built-in mechanisms.
10. Wait for a code review to come back, or an approval.
11. Either go back and fix whatever the reviewers recommend, or watch and smile as your PR gets merged in and you become part of software development history.

Version data entries

19 entries across 19 versions & 7 rubygems

Version	Path
data_janitor-0.4.0	contributing.md
data_janitor-0.3.7	contributing.md
data_janitor-0.3.6	contributing.md
westfield_paginator-1.0.7	contributing.md
service_logger-1.4.2	contributing.md
sanitize_order-1.1.3	contributing.md
status_querier-1.2.4	contributing.md
data_janitor-0.3.5	contributing.md
heroku_lockdown-4.0.3	contributing.md
westfield_swagger-1.2.6	contributing.md
westfield_swagger-1.2.5	contributing.md
westfield_swagger-1.2.4	contributing.md
westfield_paginator-1.0.6	contributing.md
status_querier-1.2.3	contributing.md
westfield_swagger-1.2.3	contributing.md
heroku_lockdown-4.0.2	contributing.md
data_janitor-0.3.4	contributing.md
sanitize_order-1.1.2	contributing.md
service_logger-1.4.1	contributing.md