2019-10-09 12:25:33 +00:00
---
path: "/docs/contributing-guide"
title: "Contributing Guide"
---
2019-10-02 10:06:47 +00:00
Thanks for taking interest in contributing to Chatwoot source code. Before submitting your contribution, please make sure to take a moment and read through the following guidelines:
2019-10-13 04:28:32 +00:00
- [Code of Conduct ](https://www.chatwoot.com/docs/code-of-conduct )
2019-11-18 16:35:10 +00:00
- [Development Setup ](https://www.chatwoot.com/docs/installation-guide-ubuntu )
2019-11-23 20:31:13 +00:00
- [Environment Setup ](https://www.chatwoot.com/docs/quick-setup )
2019-10-02 10:06:47 +00:00
## Pull Request Guidelines
2020-01-20 18:03:29 +00:00
- We use [git-flow ](https://nvie.com/posts/a-successful-git-branching-model/ ) branching model. The base branch is develop.
2019-10-02 10:06:47 +00:00
- Assign the corresponding issue to you whenever you start working on it. This helps in resolving collision (mutliple people working on the same item)
2020-01-20 18:03:29 +00:00
- Please raise the PR against `develop` branch
2019-10-02 10:06:47 +00:00
- It's OK to have multiple small commits as you work on the PR - We will squash the commits before merging.
- If adding a new feature:
2020-01-20 18:03:29 +00:00
- Please create the branch in the format `feature/<issue-id>-<issue-name>` (eg: `feature/235-contact-panel` )
2019-10-02 10:06:47 +00:00
- Add accompanying test case.
- Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
- If fixing bug:
2020-01-20 18:03:29 +00:00
- If you are resolving a special issue, add `Bug: Fix xxxx` (#xxxx is the issue) in your PR title.
2019-10-02 10:06:47 +00:00
- Provide a detailed description of the bug in the PR.
- Add appropriate test coverage if applicable.
