CONTRIBUTION.md
## How to contribute to Devist
#### **Did you find a bug?**
* **Open up a GitHub issue if the bug affects Devist**
* **DO NOT open up a GitHub issue if the bug is a security vulnerability, and instead contact author directly.**
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/stacklog/devist/issues).
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/stacklog/devist/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **changelog sample** or an **procedure steps** demonstrating the expected behavior that is not occurring.
#### **Did you write a patch that fixes a bug?**
* Open a new GitHub pull request with the patch.
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
* Devist try to have clear and consistent code. We are following [Ruby Style Guide](https://github.com/bbatsov/ruby-style-guide) code conventions.
#### **Did you fix whitespace, format code, or make a purely cosmetic patch?**
Changes that are cosmetic in nature such as grammar or whitespace are also appreciated, please send pull request.
#### **Do you intend to add a new feature or change an existing one?**
* Suggest your change with the new [Issues](https://github.com/stacklog/devist/issues/new) and start writing code.
</br>
Devist is a volunteer effort. We encourage you to pitch in and start contributing.
Thanks! :heart: :heart: :heart:
stacklog/devist