In the previous tutorial, the checkout subcommand was used to switch betweeen branches, but there’s a lot more that it can do. “Checking out” is how you switch between different points of the repository’s history. You can checkout branches, tags, and commits. Tags Tags are just named pointers to commits (with optional extra data). They’re usually used for marking versions of software, which makes it really easy to jump between versions in a git repository....

If you’ve followed along with the previous tutorials, you now know how to work with commits, stage files, view the commit log, and maybe a few other things. Now it’s time to use one of git’s most useful features: branching. What is a branch? In reality, a branch is just a named pointer to a commit. But for most purposes, thinking of a branch like a branch of a tree is fine....

What are staging areas? When you run git status after modifying some files, you’ll see something like this: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: file1.txt modified: file8.txt Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>....

Installing Git You can find Git in basically every package manager in existence. If you don’t use a package manager, you can get git from the official downloads page. This tutorial uses git version 2.x.x. Check which version you have by running 1 $ git --version Creating a repository To create a git repository in the current directory, use the init subcommand: 1 $ git init This command will create the ....

What is Git? Git is the world’s most popular version control software. But that raises another question; what is version control? Version control is a system of saving changes to files in steps. In Git, these steps are called ‘commits.’ When you use version control, all changes to your codebase are kept and are organized for you. This is extremely useful if you want to do something like roll back a change, or pinpoint when a bug was introduced....