You both are working on the same project files. So imagine you and your friend are collaborating on a project. Git also helps you synchronise code between multiple people. So I can jump to and fro to any version of the file in the git time continuum. We can select which version of the file we want to use at any point of time. In the example above, all three cards represent different versions of the same file.

A simple example of version history of a file. Or you can simply see what changes you made to your code over time. If at any point while coding you hit a fatal error and don’t know what’s causing it you can always revert back to the stable state. It is basically the history tab for your code editor(With no incognito mode ?). Git helps you keep track of the changes you make to your code. This clone has all of the metadata of the original while the original itself is stored on a self-hosted server or a third party hosting service like GitHub. Instead, every user “clones” a copy of a repository (a collection of files) and has the full history of the project on their own hard drive. So Git does not necessarily rely on a central server to store all the versions of a project’s files. Git is a Distributed Version Control System. Git is a version-control system for tracking changes in computer files and coordinating work on those files among multiple people. And sometimes you just want to know “who wrote this crap”, and having access to that information is worthwhile ?. Using a VCS also means that if you screw things up or lose files, you can generally recover easily. Umm… Okay… But Why Tho? Here’s Why:Ī Version Control System (VCS) allows you to revert files back to a previous state, revert the entire project back to a previous state, review changes made over time, see who last modified something that might be causing a problem, who introduced an issue and when, and more. So ideally, we can place any file in the computer on version control. Let’s get started! What is Version Control? Version control is a system that records changes to a file or set of files over time so that you can recall specific versions later. But in this guide we’ll be using GitHub to understand Git. The technology is all the same no matter the client. This is a comprehensive beginner’s guide to Git.

If you want to get started on learning about Git technology, you’ve come to the right place. But you can get pretty close in about 25 minutes. There is no way you can understand the basics of git technology in just 10 minutes. By Gowtham Venkatesan Learn the Basics of Git in Under 10 Minutes

Best git gui windows free