Contributing to RouteTranslator

Looking to contribute something to RouteTranslator? Here's how you can help.

Reporting issues

We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems that we can fix within the RouteTranslator core. Please read the following guidelines before opening any issue.

Search for existing issues.
Create an isolated and reproducible test case.
Include a live example if possible.
Share as much information as possible. Include at least Rails version and gem version. Also include steps to reproduce the bug.

A Bug Request Template will guide you in the creation of a good bug report.

Key branches

master is the latest, deployed version.
develop is the official development branch for the next release.

Take a look at git-flow, A successful Git branching model

Pull requests

If your PR fixes bugs or documentation, pull against the master branch
If your PR includes new features, pull against the develop branch
Try not to pollute your pull request with unintended changes--keep them simple and small
Test. If you find a bug, write at first a failing test case and then fix it.
We are open to discussion. If you have troubles or questions, feel free to start a new issue

Coding standards

Ruby

Ruby Styleguide

Commits

How to Write a Git Commit Message

License

By contributing your code, you agree to license your contribution under the terms of the MIT License

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!