Introduction to GIT Version Control

Life was easy, projects were small; there weren't more files to handle and tracked for changes. Many project files got misplaced and many got deleted. A part of hard work couldn't be saved because of lack of knowledge. Saved works couldn't be indexed so that I could access different versions of my code within same repository.

HEARD OF VERSION CONTROL SOFTWARE LONG AGO, BUT COULDN'T GRAB THEM FOR PRACTICAL USE.

Now here comes the requirement of version control software and lets get started.

Git is the  most popular version control software that helps to track different versions of  our code and let us move back and forward to different versions. So, in case we get messed up with our code and need to get some previous working versions of our code, its GIT that provides us the power to get our requirement.

GIT helps us to track every changes made in our project directory. It creates something like mapping of the changes made in our projects. And we can navigate to different locations in the map created by git to undo changes or redo changes made.

GIT uses three layer architecture for version control mechanism namely working, staging index and repository. When we make some changes in our project directory, the files are in the "working" state. After we call "git add" command these changes are shifted to the "staging index" and finally on "git commit" command, they are moved to the "repository". Likewise all the files use this three layer workflow.