A separate GitHub repository is created to manage each openIMIS component, e.g:
web_app_v
web_service_vb
rest_api_c-sharpopenimis-be_py
etc
The naming of repository generic naming convention for openIMIS modules is based on the template: "component name"_"programming language / technology" openimis-<fe | be>-<module name>_<js | py>.
We use the Gitflow Workflow, which was first published in 2010 in a blog post from Vincent Driessen at nvie. We have extended this workflow to include country implementation specific version versions of the component managed through the repository.
...
Each new feature are developed in its own branch and then integrated into the develop branch. The naming convention for the feature branch is feature/<name of the feature | Jira ID>. Whenever possible, use Jira ID for the name of the feature that facilitate easy GitHub-Jira integration and generation of release notes.
When enough features are available, a release branch is created from the develop branch. Only bug fixes can be added from this point to the release branch, which will also be merged into the develop branch. The naming convention for the release branch is release/<release version>.
As soon as a release is ready, it will be merged into the main and will be tagged with a release number.
...