The easiest way to illustrate CI/CD would be walk through the policies and procedures, starting with GitFlow. Here, we are dealing with two separate repositories, namely, web and application, and each of these repositories have their own life cycle.
In other words, while it is not advised, it is possible to have unsynchronized releases and versions of our web application (that is, the service infrastructure) and application (that is, mobile platform releases); hence, it is important to create backward-compatible modules and communicate releases to development team members.
Development of the application or web modules start with the creation of a feature branch (for example, feature/12345
). The feature branch can be shared between multiple developers or handled by a single developer. If the feature branch is being worked on by multiple developers, user branches can be created following a similar convention along the lines of user/<user identifier>/<feature...