Do you have a large project in hand and you don’t know how to coordinate your team? To this end, there are different remote repositories which allow coordinating the whole team. In addition, once the project has been launched, we may want to introduce changes which weren’t previously considered or to include new functions. For these reasons, it is advisable to implement a central working model which, in our case, happens to be the Git Branching Model
What if we implemented descentralised model? We could find that new functions contain errors or that different programmers have overlapped each other’s work. Moreover, if users are constantly spotting those errors, company and product image and reputation may result damaged.
To prevent this, eHidra implemented this working method in which new functions and errors spotted after launch are constantly checked. How? By using a remote repository such as GitHub.
Git Branching Model: Working environments
To make all those checks possible, different working environment are needed. We organise it as follows:
We can keep our project code in remote repositories and make it accessible for the rest of the team. In this way, it is possible to work simultaneously. GitHub allow creating the so-called branches in order to avoid overlaps when working. We will have two main branches:
In the first one, there will be those changes to introduce, while in the second one there will be the source code ready to run.
A clear distinction according to issue should be made between the three types of secondary branches.
Programmers will create secondary branches in the development branch for each error in the remote repository to be fixed. In this way, each branch will contain all information in the develop branch, as well as the code added by the programmer without affecting other team members.