toy example of collaboratively putting together an Ecosystem Status Report
- Start a new branch for features; in our case a new indicator
- In that branch, you should only update that indicator
- Collaborators should not work on the same branch at the same time to avoid overlapping code or conflicts
- When the indicator is ready to be added, the team member responsible for it should submit a pull request
- The request has to be approved by the repo admin before it is merged and the branch is deleted.
- Do this for all the indicators; there can be many branches and merging should be straightforward if the new code is only for that indicator and is not working on other dependencies within the repo
- eat some coconuts
- grow a coconut tree
##ADDING!