From 51fda9a0160b8aabd485a83233ad2dd11caebb4d Mon Sep 17 00:00:00 2001 From: Bruce Cabanayan Date: Sat, 30 Jun 2018 13:10:19 -0700 Subject: [PATCH] made changes to the README --- README.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index c4dcbed..1640f67 100644 --- a/README.md +++ b/README.md @@ -1,15 +1,15 @@ # Pre Course Git Fu [Pre Class Video](https://youtu.be/ZihgMcrHOF4) ## Terms for learning Git - * Repository - - * Git - Version Control - - * Clone - - * Fork - - * History - - * Staging - - * Remote - - * Commit - - * Push - + * Repository - a folder in which all of a project's files are located and can be accessed by collaborators + * Git - Version Control - the practice of tracking the changes made to files and the different versions of files; Git is a program that enables for this tracking + * Clone - a copy of a file that is stored on an individual collaborator's local machine, instead of a server + * Fork - a copy of a file that is stored on a collaborator's GitHub account, which can be edited without affecting the original copy + * History - a record of the changes made to the original by a collaborator + * Staging - the process of reviewing the changes made to the version control file in a clone and cleaning the history before committing any changes + * Remote - describes the files that are hosted on a server, versus the files stored on an individual collaborator's computer + * Commit - saving changes made to a file and recording those changes for version control + * Push - uploading a file with changes to a repository, like one on GitHub, for review ## Steps to our Lamba School Git Flow 1. Fork repository