Reader small image

You're reading from  GitLab Quick Start Guide

Product typeBook
Published inNov 2018
PublisherPackt
ISBN-139781789534344
Edition1st Edition
Tools
Concepts
Right arrow
Author (1)
Adam O'Grady
Adam O'Grady
author image
Adam O'Grady

Adam O'Grady hails from the remote Perth, Western Australia, and can usually be found on Twitter at @adamjogrady or in meatspace wrangling with code. His first taste of programming came from building games into graphics calculators at high school, and quickly developed into a passion. A few years later, while doing social media marketing for an ISP, his first big break arrived; building custom applications to monitor and respond to social feeds. After that, he spent a few years working for the government building systems that used satellite and geographic data to spot and predict bushfires, and now you can find him leading a small team of engineering mavens at a local health start-up.
Read more about Adam O'Grady

Right arrow

GitFlow

Git flow is a semi-standardized workflow for dealing with projects in Git. It can be daunting, but the rules involve creating a stringent practice for when branches should be committed to or merged in order to prevent deploying buggy code or releases. A diagram of it is as follows:

As you can see, there are a number of different streams. You have the master branch, hotfix branches for fixing emergency bugs, releases, the develop branch, and feature branches. These all have very particular uses, which we'll go into now.

Master

The master branch is the original branch where all code is branched from. However, it is never committed to directly; it is only ever merged into. The master branch is then used as the deployed...

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
GitLab Quick Start Guide
Published in: Nov 2018Publisher: PacktISBN-13: 9781789534344

Author (1)

author image
Adam O'Grady

Adam O'Grady hails from the remote Perth, Western Australia, and can usually be found on Twitter at @adamjogrady or in meatspace wrangling with code. His first taste of programming came from building games into graphics calculators at high school, and quickly developed into a passion. A few years later, while doing social media marketing for an ISP, his first big break arrived; building custom applications to monitor and respond to social feeds. After that, he spent a few years working for the government building systems that used satellite and geographic data to spot and predict bushfires, and now you can find him leading a small team of engineering mavens at a local health start-up.
Read more about Adam O'Grady