Scribd
Upload
28 views1 page

Adobe Scan 16 Mar 2023

Git is a source code management tool used for version control. It uses a branch-based workflow where developers create feature branches off the develop branch to work on new features. Once completed, they merge the feature branch back into develop. When a feature is ready for production, it is merged into the master branch and deployed. If a critical issue arises in production, a hotfix branch is created from master to fix the issue, then merged back into both master and develop.

Uploaded by

abhi.may011
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views1 page

Adobe Scan 16 Mar 2023

Git is a source code management tool used for version control. It uses a branch-based workflow where developers create feature branches off the develop branch to work on new features. Once completed, they merge the feature branch back into develop. When a feature is ready for production, it is merged into the master branch and deployed. If a critical issue arises in production, a hotfix branch is created from master to fix the issue, then merged back into both master and develop.

Uploaded by

abhi.may011
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

I Git

git = git is a source code management tool / version control tool

i{ancfii~;itrat~
·. •;i·-.)\ ~
"'· .
,.. • .- ...- ·
. · . .
.. ~-• .·..• . ... •• . .. -. .·,~·i.•~1.1
. •·. i~_-'

Yeah well, in our previous project we do have master branch for production
deployments and develop branch for dev deployments.

For development, developers are cut the develop branch and creates feature
branch and start working on developing their feature of application. Once they finish
writing code they used to push the code to their respective branches and raise the PR's.
Once PR is reviewed then they used to merge the feature branch to develop branch.

Similarly, when particular feature of application is ready for production, then they
will raise PR for Master branch, after verifying the PR thoroughly, code will be merged to
master and this code will be deployed to production environment, after taking CAB
approvals from managements.

Any major/critical issue arises in production environment, Incident management


team will raise ticket and respective team will starts fixing the issues.

In this case developer will cut the master branch and create hotfix/patch branch and
started fixing the issue. Once fixes are done, new fixes are verified and well tested,
immediate PR will be raised for Master branch and merged the code after reviewing it
thoroughly.

And this latest changes will be deployed to production.

Once application is working good, once everything goes well then we used to merge
the hotfix/patch branch to develop branch also, to make sure hotfix changes should be
there in develop branch. Now developer will again cut the develop branch and create
feature branch for developing next feature of application.

Master Holfix/Patch

Holfox Deployments

Featuro/appl Featuro/opp2

Developer 1 Developer2

Normal Deployments

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy