{"id":1103,"date":"2022-06-06T09:30:26","date_gmt":"2022-06-06T09:30:26","guid":{"rendered":"https:\/\/www.checkmateq.com\/blog\/?p=1103"},"modified":"2023-08-07T08:53:43","modified_gmt":"2023-08-07T08:53:43","slug":"git-branching-strategies","status":"publish","type":"post","link":"https:\/\/www.checkmateq.com\/blog\/git-branching-strategies","title":{"rendered":"Git branching Strategies"},"content":{"rendered":"

What is a branching strategy?<\/strong><\/h3>\n

Branching <\/b>is a process of duplicating source code stored in version control or SCM, branches allow you to develop your software<\/a> features parallelly, when you or your team members creates a branch from master\/main branch you can work on all the files or data of master branch from the child branch, this allows you to isolate your changes from the master branch. if your work\/experimentation goes well you can merge your changes, if your wok fails you can discard the branch.<\/p>\n

Git Flow:<\/strong><\/p>\n

Git Flow is a branching strategy considered to be complex process of all available branching strategies, developers can work on new features by creating feature branch and once changes are done these features can be merged with master branch to deploy. git flow has main, develop, feature, release and hotfix branches and the process happen as following.<\/p>\n

\"\"<\/p>\n

Master\/Main<\/strong>\u00a0 branch is where the code should be in a deployable stage and will be created when a repository is created, Develop <\/strong>branch is branched from main \/master all the developers will have this branch in common and and every developer can create a Feature<\/strong> branch from develop branch there can be any number of feature branches, you keep adding commits to feature branch\u00a0 and when you think feature is complete you will raise PR where your team will review your code and merge it back to develop branch once develop has enough features\u00a0 any type of testing or quality analysis can be done at this point, once approved\u00a0 feature branch is merged to Release<\/strong>\u00a0 branch, release branches are created\u00a0 with\u00a0 a version tag like 1.0,2.0\u00a0 after verification and testing release branch will be\u00a0 merged to master for deployment and\u00a0 develop branch to make the latest release version available for developers to work on.<\/p>\n

Hotfix branch:<\/strong>\u00a0 in a software you may have a critical issue sometimes which needs to fix instantly and cannot go through all the above-mentioned flow, so a hot fix branch is created from main branch and work will be done on the bug\/issue reported once the problem is fixed then the hotfix branch is merged with main branch for release and to develop branch for developers to work on.<\/p>\n

GitHub Flow:<\/strong><\/h3>\n

GitHub Flow is a simpler and faster alternative to Gitfow this model doesn\u2019t have release branches, you start with the main branch, to isolate their work developers create branches directly from the master and once this individual branch that a developer is working on comes to a deployable state a PR(Pull request) is created by developer, the updated code is reviewed and merged back into main for deployment with version tags.<\/p>\n

The main idea behind this model is keeping the master code in a constant deployable state and to support continuous integration and continuous delivery processes, by deploying a small pieces to production constantly you can eliminate a lot of chances for errors and in case of a failure recovery is fast as you just need to roll back to previous version.<\/p>\n

Steps and Git Commands for following a GitHub Flow<\/strong><\/p>\n

Step-1: Add collaborators to your remote repository.\u00a0<\/strong><\/p>\n

To follow any branching strategy, you have to allow your teammates to work on the project repository by adding collaborators, below is the process for adding collaborators in GitHub, on your remote repository click on settings<\/p>\n

\"Git<\/p>\n

 <\/p>\n

Now click on collaborators under access then under manage access add users that you want to collaborate with<\/p>\n

\"\"<\/p>\n

here search for the git hub user for whom you want to give permission on you repo and add them to your repository<\/p>\n

\"\"<\/p>\n

Step-2: Share your repository with your team\u00a0<\/strong><\/p>\n

share your repository link with your team so that they can clone your repo and start working on it, on your remote repository got to code\u00a0<\/strong>to get your project repository link.<\/p>\n

\"\"<\/p>\n

Step-3: Creating a branch in local repository and pushing it to remote repository<\/strong><\/p>\n

Now let’s go through some of the git commands that you need to know to follow GitHub flow.<\/p>\n

To clone a repository, use command “git clone” with the url of the repo.<\/p>\n

git clone https:\/\/github.com\/aksshaayDev\/project-webFeature.git<\/pre>\n
\"\"<\/p>\n
Here I cloned “project-webFeature ” repository to my computer and it has a html file named hello.html with content as shown below.<\/p>\n
\"\"<\/p>\n
Git commands to create and check branches in your local repo.<\/strong><\/p>\n
git branch\r\ngit branch branch2<\/pre>\n
“Git branch” gives you all the available branches on your local repository, you can also create a new branch with same command by giving a name along with the command, “branch2” is the name of branch I gave.<\/p>\n
\"\"<\/p>\n
Git command for switching to a newly created branch on your local repo<\/strong>.<\/p>\n
git checkout <branch-name>\r\ngit checkout branch2<\/pre>\n
“git checkout” is the command and “branch2” is is name of a branch<\/p>\n
\"\"<\/p>\n
then you can work on your code without affecting main branch, and to commit your changes\/updates use below commands.<\/p>\n
Git commands to commit changes<\/strong><\/p>\n
git add <file name>\r\ngit add .\r\ngit status\r\ngit commit -m 'updates to hello.html'<\/pre>\n
\"\"<\/p>\n
git add\u00a0<\/strong>will add files to staging or indexing area, staging area is where git stores the changes you can add and remove changes from the staging area, give a file name to add a particular file to staging area or you can use (.) to add all the files in that directory to staging area.<\/p>\n
git status <\/strong>is used to display the state of staging area and state between “git add’ and “git commit” commands.<\/p>\n
git commit\u00a0<\/strong>Git considers each commit as a check point you can go back to this point if want to make any changes or if you find any bug use option “-m<\/strong>” to add a message every time you commit it will help you to find out what was changed from previous commit.<\/p>\n
Git command to push locally created branch to remote repository<\/strong><\/p>\n
To push your local branch to remote repository, use the following command<\/p>\n
git push -u origin branch2<\/pre>\n
To understand above command lets break down it, git push\u00a0<\/strong>will transfer commits from local repo to remote repository and git push origin <\/strong>pushes the branches to main branch and the flag -u<\/strong> creates a reference to track your branches that you push onto your remote repository.<\/p>\n
when you make changes in master\/main branch and push them, changes will directly reflect but when you push a branch you have to raise a PR (Pull Request) where a discussion can be happened on the bugs\/features and any one with push privileges can merge it with main, see below for the process to raise a PR.<\/p>\n
Step-4: Create Pull Request<\/strong><\/p>\n
pull request is an event in Git where a contributor of repository asks owner of git repository to review code they have pushed and merge it into main\/master branch, follow the process to raise a PR, on your remote repo click on branches beside main<\/p>\n
\"\"<\/p>\n
and click on “New pull request” of the branch that you are working on<\/p>\n
\"\"<\/p>\n
here you can write your comments and click<\/a> on “create pull request”<\/p>\n
\"\"<\/p>\n
and any one with merge privileges can review your changes and merge them to main branch, check below process to merge a PR.<\/p>\n
Step-5: Merging a Pull Request<\/strong><\/p>\n
on remote repo go to Pull requests<\/strong>, here you can check the details and merge pull requests.<\/p>\n
\"\"<\/p>\n
\"\"<\/p>\n
 <\/p>\n
Author Note<\/strong><\/p>\n
This blog is written by M\/S Checkmate Global Technologies engineering team, You can please connect with engineering team to hire experienced DevOps engineer<\/a> on part-time\/full-time\/Project basis. Our Technical Consultant are ready to share vetted engineer profile instantly.<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
What is a branching strategy? Branching is a process of duplicating source code stored in version control or SCM, branches allow you to develop your software features parallelly, when you or your team members creates a branch from master\/main branch you can work on all the files or data of master branch from the child … Continue reading “Git branching Strategies”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":1303,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[2,23,16,24,8],"_links":{"self":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1103"}],"collection":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/comments?post=1103"}],"version-history":[{"count":35,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1103\/revisions"}],"predecessor-version":[{"id":4323,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/posts\/1103\/revisions\/4323"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media\/1303"}],"wp:attachment":[{"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/media?parent=1103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/categories?post=1103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.checkmateq.com\/blog\/wp-json\/wp\/v2\/tags?post=1103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}