###Pull-Request template
Requires Two Reviews to merge Pull-Request
Pull Request
- Has a clear title and clearly state the reason for the pull request (what does the feature do)
- Example of branch naming: TypeOfChange/Feature
-
Commits have a short description to what was done
-
PR is relatively small. Try to focus on only changing code relevant to feature being worked on in specifc PR.
-
Format of code is consistent in project
-
Code follows best practice
-
Review has feedback