The choices teams made when setting up their workflow, and the reasons for those choices, get forgotten and are rarely revisited.

Version control is fundamental to DevOps, so using it becomes second nature for DevOps teams. But the choices teams made when setting up their workflow, and the reasons for those choices, get forgotten and are rarely revisited.

Gearset operates in an ecosystem where many development teams are still adopting DevOps. As a result, we spend a fair amount of time helping teams move from manual deployments and slow release cadences to a mature DevOps process. Even though their priorities and challenges vary, teams in small startups and large enterprises alike are all looking for the same thing: the agility that comes from DevOps.

Adopting version control is the first step on the journey for these teams, and we guide them on the way. Usually, the most involved part of this process is a discussion about Git branching strategies. We think the advice we give holds true for any teams looking to revise or implement their own Git branching strategy.

Take One Step at a Time

Question Your Current Process

Adopt the Simplest Possible Git Branching Strategy

Don’t Impose a New Strategy Without Buy-in From the Team

Getting the Right Balance

#devops #git branches #git