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

Authorize access to VSTS REST APIs with OAuth 2.0

Visual Studio Team Services uses the OAuth 2.0 protocol to authorize your app for a user and generat...

Read More >

What is Synchronization? Handling Synchronization in Selenium WebDriver using C#:

Synchronization meaning: when two or more components involved to perform any action, we expect these...

Read More >

Wireless Ad-Hoc distribution for iOS apps

Creating Ad-Hoc is an important part of iOS app development because it helps us in testing the app d...

Read More >

How to do Installation of K8S using kubeadm?

Till now I have given blogs on k8s objects, services, namespaces, ingress etc. but where to execute ...

Read More >

VSTS Area Uploader

VSTS Area Uploader helps you to upload Areas (with multiple level) to your VSTS Team Projects from a...

Read More >

Creating an RDLC report in Asp.Net

Step 1.  Create a new website and Add DataSet to the WebsiteRight Click on the project, Add new...

Read More >

HOW TO DO BACKUP AND RESTORE ENTIRE K8S CLUSTER?

If you have deployed different applications on k8s cluster using various objects like deployments, p...

Read More >

Using XMPP and Openfire Server in Windows Phone 8

Implementing Extensible Messaging and Presence Protocol (XMPP) in Windows phone 8 is really a tough ...

Read More >

Create a Windows Server 2012 R2 VM using ARM in Azure PowerShell

Hi Folks,In this Blog Post we will learn how to create an Azure ARM Virtual Machine using Azure Powe...

Read More >

Share

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

Sign Up

  • Recent
  • Popular
  • Tag
Tags
Monthly Archive
Subscribe
Name

Text/HTML
Contact Us
  • *
  • *