Contents

# Contributing

## First

* Check if the issue you're going to submit isn't already submitted in
  the [Issues](https://github.com/aziz/tmuxinator/issues) page.

## Issues

* Submit a ticket for your issue, assuming one does not already exist.
* The issue must:
  * Clearly describe the problem including steps to reproduce when it is a bug.
  * Also include all the information you can to make it easier for us to reproduce it,
    like OS version, gem versions, rbenv or rvm versions etc...
  * Even better, provide a failing test case for it.

## Pull Requests

If you've gone the extra mile and have a patch that fixes the issue, you
should submit a Pull Request!

* Fork the repo on Github.
* Create a topic branch from where you want to base your work.
* 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!
* Run _all_ the tests to assure nothine else was broken. We only take pull requests with passing tests.
* Check for unnecessary whitespace with `git diff --check` before committing.
* Push to your fork and submit a pull request.

Version data entries

5 entries across 5 versions & 1 rubygems

Version	Path
tmuxinator-0.6.4	CONTRIBUTING.md
tmuxinator-0.6.3	CONTRIBUTING.md
tmuxinator-0.6.2	CONTRIBUTING.md
tmuxinator-0.6.1	CONTRIBUTING.md
tmuxinator-0.6.0	CONTRIBUTING.md