Git Workflow Setup

In this blog post I will introduce you to a Source tree feature that will ease the process of adhering to a GIT work flow. This feature was created to ensure everyone on your team adheres to the GIT workflow process and automates a lot of the work so that you can focus more and development and spend less time managing GIT.

1- Sign up to Bitbucket, create a new repository and open it using source tree as shown below.

Screen Shot 2015-03-08 at 4.38.16 PM

 

2- Insert your project files and lets get started. When you first click on “Git Flow” on the top right, a modal like the one below will appear with default conventions used recommended by Source Tree, feel free to change any naming conventions; bear in mind that everyone on your team must follow the same conventions (good idea to discuss it first). Notice how feature is followed by a front slash, this will simply create a folder called feature which will host all feature branches of your development, same principle goes to hotfix and release branches.

Screen Shot 2015-03-08 at 4.44.12 PM

I do recommend having a prefix for hot fix, release, and feature branches; this will help you group them together for easier access  in the future. Below is the naming conventions this feature will help you maintain in the development process.

  • Hot fix and Release branches will always be named according to the version number you assign it.

In the next few posts I will be walking you through all the situations that GIT flow simplify. Please like and share this post if you found it useful.

 

 

 

Michael Ghattas

Tech guy deeply interested in startups, growth, AI and just anything exciting. Currently involved with MTL New Tech and Wavo.me. Love travelling and exploring new cultures. In my spare time I like to read, write, code, and just hang out with friends. I actively trade the stock market and will be talking about my trades in the blog.

GIT