Background

These notes are provided to demonstrate how to get started with GIT, and to introduce the terminology and principles of using code repositories. When I'm coding in a modern project and I'm working within a single company, I will always have a repo to allow for version/revision/source control. This is the management of changes to documents, including who and made changes and when, and what was changed.

In the old days, I used to have a folder in every project called Archive. At the start of each days work, I would save the current version in a dated folder. Very cumbersome, but it gave me some possibility to roll back changes. I used this methodology for project documentation AND code.

These days, I use GIT version control for all these things. It also facilitates team work, in a way single file shares never could. On a new project, I'll set up the repo on a local server and as I induct other coders to the project, I'll give them read/write access permissions.

GIT and GITHUB are two completely different things! Do not concern yourself with GITHUB for now, this will be covered in a separate exercise.