it is important to understand the basics of Git version control. There are a parcel of individuals that utilizes IDE's and visual instruments to do the essential tasks like commit and push changes, make and union branches, think about history and return changes, without figuring out how Git really works. The expanding technique relies upon the span of your group, the number of groups taking a shot at the venture, if the undertaking has more than one element being created in the meantime, the recurrence you discharge code to generation… the more unpredictable your situation, the more you depend on an appropriate branch methodology to help it

There are three popular branching models in GIT.

• A component branch MODEL keeps the majority of the progression for a specific element within a branch. At the point when the element is completely TRIED and approved via computerized tests, the branch is then converged into an ace.

• In this model, each undertaking is actualized without anyone else branch with the assignment key incorporated into the branch name. It is anything but difficult to see which code actualizes which task, simply search for the undertaking key in the branch name.

• Once the CREATE branch has gained enough highlights for a discharge, you can clone that branch to shape a Release branch. Making this branch begins the following discharge cycle, so no new highlights can be included after this point, just BUG fixes, documentation, and other discharge situated assignments ought to go in this branch. When it is prepared to DISPATCH, the discharge gets converged into an ace and labelled with a variant number. Moreover, it ought to be converted once again into creating a branch, which may have advanced since the discharge was started.