# Git Definitions

**Instructions: ** Define each of the following Git concepts.

* What is version control?  Why is it useful?
* What is a branch and why would you use one?
* What is a commit? What makes a good commit message?
* What is a merge conflict?
# Git Definitions

**Instructions: ** Define each of the following Git concepts.

* What is version control?  Why is it useful?

  Version control enables you to take snapshots of your work as you make changes on a project. It's useful because you can revert your work back to an earlier version if your latest updates create bugs or errors. It also serves as a back up of your work.

* What is a branch and why would you use one?
  
  A branch is a copy of the master version of your project. It's useful because it enables you to work on a new feature in a safe way. The master version is not affected by any changes you make on the branch, until you merge the branch back into master. At that point, if any errors or conflicts are found, they can be resolved before being merged in the master branch.

* What is a commit? What makes a good commit message?
  
  A commit when you merge the changes you've made on a branch back into the master branch. This ensures that your master branch is up to date with the latest changes. A good commit message is written in present tense and explains what specific changes you've made. 

* What is a merge conflict?
  
  A merge conflict is when two branches have changed the same part of a file. For example, if two developers branch off master and are told to fix the error on line #12, they might fix the error in two different ways. Then, when they both try to merge back into master, Git won't know which version it should use and will throw a merge conflict error.
Add definitions to git terms
Add definitions to git terms
