Contributing

Style Guide

Please follow coding convention and style in each file and in each library when adding new files. Please also refer to the overall project guidelines

All development on ForestFlow should happen in a separate branch with 'develop' as the base branch.
We recommend positing issues on GitHub for features or bug fixes that you intent to work on before beginning any development. This keeps development open and conversations and feedback more collaborative.
Pull requests should be rebased on the latest dev commit and squashed to as few logical commits as possible, preferably one. Each commit should pass tests in isolation.
Please make pull requests as small and atomic as possible. We will only consider pull requests that have an associated GitHub ticket.

Raise a new GitHub issue if one does not already exist. Mention that you intend to work on it.
Use GitHub to Fork your own private repository
Clone your forked repo locally
You can optionally add ForestFlow's repo as upstream to make it easier to update your remote and local repos with the latest changes
```
# cd into your local git copy
cd ForestFlow
git remote add upstream https://github.com/ForestFlow/ForestFlow.git
```
Fetch latest from upstream
```
git fetch upstream
```
Create a new branch for each feature and provide a descriptive name, preferably the GitHub ticket number. This will checkout a new branch and create it simultaneously:
```
git checkout -b github-1234 upstream/develop
```
Write your feature code and update any documentation under ./docs and test it builds without errors

Commit and push your code branch

git commit -m "Descriptive message here"
git push origin github-1234