kaleidoscope

In the  last post , we discussed  git internals  to understand Git. In this post we will discuss Git commands, to use Git. I recommend reading the last post, to easily understand the terminologies used here. I’m going to skip the commands to install git as it varies based on the operating system and y. Once you have our machine architecture. After installation following are the commonly used commands. 1. Check Git Version git —-version   check and confirm the installation 2. Configure Git You can use the below command to set global configurations for Git. git config --global  key “value” . By default, Git doesn’t allow you to commit until it knows who you are. So the first thing to do after installation is, to set the below properties. Preferably globally git config --global   user.name  “My Name” git config --global   user.email  “ myemail@email.com ” NOTE . If your  present working directory  is inside a local git repository, you can omit the  —-global  option from the above command

Since the dawn of software engineering, managing the source code had been a great challenge for engineers. A plethora of  Source code management (SCM) systems & Version Control Systems  ( VCS ) have been developed in the search for the best one. In my short career, I have used the useless  Microsoft VSS , the ubiquitous  CVS , the slightly better  SVN,  and the proprietary  IBM-ClearCase . But none provided as comprehensive a solution as the one and only  GIT . The Evolution The quest for the best SCM ended in  2005  when  Linus Torvalds  gave another opensource gift to the world. It was a source code management system (SCM) that he created to manage the  distributed development  of the Linux kernel's huge codebase .  He named the SCM  GIT . The industry embraced  GIT  with open arms. SAAS providers like  GitHub ,  BigBucket  &  GitLab  added more bells and whistles on top, and within a few years,  GIT  became the ubiquitous source control solution. Git Architecture Git is