August 2019
Beginner
482 pages
12h 56m
English
The main idea behind Git is to store code in atomic snapshots—commits. Ideally, every commit should represent one logical step in development—say, an addition of one function. For each commit, you can add a message, explaining the change. They can also be tagged. This tag can be later used for ease of navigation between commits. When committed, files are archived in a special folder, named after the commit hash. Git keeps track of all the files that were changed, and stores a copy of only those in a new commit. You can always switch to another commit, revert code to the previous state, look at the history, or create "diffs," side-by-side comparisons of what changed between the two versions of the file.
Another important concept is ...