Developers ‐ EcoMind development workflow
The next figure shows the Ecomind development workflow strategy. This strategy is based on a forking workflow.
The branches presented in the previous figure are explained next.
- SASVAR-Project/Ecomind/main: it is the main branch. This branch is used to contain the Ecomind stable versions.
- DeveloperRepo/Ecomind/main: it represents the developer own repo, in which each developer develops the new functionalities or code updates.
As you can see in the previous figure, developers have to fork the Ecomind/main branch, in order to develop their own functionalities. We suggest you to read the forking workflow documentation in order to understand how this approach works.
Finally, you can see that there is a main process in the Ecomind development workflow figure. That process is explained next.
Once a developer pull-request is submitted (to the Ecomind/main branch), a Ecomind reviewer checks the pull-request:
- If the code seems to be OK, the Ecomind reviewer accepts the pull-request and the EcoMind-continuous-integration-and-deployment process is executed.
- If the code presents errors, the Ecomind reviewer rejects the pull-request and explains the decision to the developer.