a cute git logo

In our software engineer life, the most important tools as I think are not newest and trending ones. Instead, they are our daily and basic tools, and mastering them is a nontrivial task. One of these tools is Git. We know and use it everyday but not all of us understand it clearly and know how to use it correctly.

All of our daily workflows should be standardized because it ensures the workflow inputs and outputs to be consistent every time. Besides, it saves our time and our brain’s memory which will be allocated to new awesome things but not repetitive and boring ones.

Following a standard Git branching will free you from conflicts s and give you a really smooth releasing flow. Below is just a really small and old thing about Git branching model that I write down to remind myself and hope it helps others. It completely follows Vincent Driessen’s Model which can be applied for general software development. In this post, some detailed steps are added for mobile developers.

Firstly, assume that you app is in development stage or has been released several version. We have two main branches( master and develop) currently.