Git works differently than the version control systems the precede it. This is the feature that will be most used by an FTC team (since the first feature is more useful in projects with many, many coders).
The other main feature of version control software is that it allows multiple developers to work on one code base, and receive the code changes that others make. Version control is the concept of storing different versions of a piece of software as it is developed, so that if a bug is discovered in a piece of code, its origin can be identified, and the previous version of the code can be looked at to see how the bug could have developed. There are essentially no exceptions to this, and when there are, I will point it out. When reading this guide, after any command which is to be typed into the command line, it is implied that you press enter. Git attempts to solve many of the problems posed by earlier version control systems, and in the author's opinion, succeeds at this.
Git is a free software version control system initially developed by Linus Torvalds to help him create his more well-known project, Linux.
The same argument applies for LabVIEW files. This could also be used for CAD files, but it is not recommended, since CAD files are binary data which is not handled well with traditional version control systems. This guide is for anyone who would like to use the version control system git with RobotC in an FTC environment.