Source Code Management Tool – GIT (version control) - Blogs
X
20Jul

Source Code Management Tool – GIT (version control)

 

  • This blog is all about discussing the tool which is highly used in IT sector as source code management tool and version control kit that is git. Git tool is highly used because of its light weight and its high efficiency for the duplication of the source code into various branches  
  • The git is known as version control system also because it can record all the changes we made in the source code . It can be recalled whenever it is needed 

  • The local repository using the code can be having a updated version and the past versions so that the code can run in all kinds of environments without any disturbances 

  • The git is mainly used for managing and interpreting the source code. And it is done by creating various branches in the terminal according to the project and source code`s requirements. 

git1

 

The above flow diagram is the correct depiction of git flow strategy used in various organization for the efficient usage of the source code. 

  • Master branch: it’s the default branch for the source code that must be intact or untouched. 

  • Development branch: it’s the permanent branch after master , where the devops guys have to edit the source code. 

  • Release branch: the purpose of this branch is to fix the bugs before releasing the update in the deployment.   

  • Hotfix branch: this is about the fixing the bugs or software glitches at the deployment stage. 

  • Feature branch: it is the sub-branch of development branch, this is branch with numerous branches of several feature update required to source code. 

  •  Support branch: it is the branch for the older versions which are not in trend, used for the new versions update. 

 

The below picture shows the work-flow of git branches and the how branching strategy works:  

  • Master branch is the main branch to contain the source code and we create other branches for replicating the source code and using the code according to the update required in each particular-branch. 

  • Then, the code which has been bisected and updated in every branch will be merged into the master branch then, the code will be committed and pushed to remote repository in GitHub further usage of the code. 

git2

Related

SVG Image and advantage

          "SVG images one of the best way to do full resolution graphi...

Read More >

How to Remove the Departments Action Button in NAV 2015

Some customers may not want to use Departments menu available. We need to have some option to remove...

Read More >

Dynamics Team commences work on NAV Version Migration for a prestigious client in Malaysia

Canarys Dynamics Team is all excited and geared up to commence work on NAV Version Migration project...

Read More >

What's New In C# 6.0?

Microsoft has released the preview version of Visual Studio 2015 and .NET 4.6 for developers to try ...

Read More >

Azure App Service (Build And Host Web Apps, Mobile-Back Ends Without Managing Infrastructure)

In this blog we will see what is Azure App Service, and it’s  features and why do we use it, we can...

Read More >

Microsoft Azure Stack : Power of Azure in our datacentre

Why Azure Stack?Microsoft Azure Stack is a new hybrid cloud platform product that enables our organi...

Read More >

Single Team Project Migration from TFS to Azure DevOps Services

Does your client want to break out from the existing older version of TFS (2015 and later) to Azure ...

Read More >

What’s new: Extension for Microsoft Dynamics NAV 2016

We all have seen the situation where we need to put in lot of efforts to modify the standard NAV obj...

Read More >

Share

Try DevOpSmartBoard Ultimate complete Azure DevOps End-to end reporting tool

Sign Up

  • Recent
  • Popular
  • Tag
Monthly Archive
Subscribe
Name

Text/HTML
Contact Us
  • *
  • *