# 1.5 Tracking Changes Reflection
* How does tracking and adding changes make developers' lives easier?
  * Tracking and adding changes allows developers to keep track of when certain features were added.  This can help you to revert changes to an appropriate version.
* What is a commit?
  * A commit is submitting a series of changes to the repository.
* What are the best practices for commit messages?
  * Commit messages should be short and to the point.
* What does the HEAD^ argument mean?
  * HEAD^ refers to the last commit.
* What are the 3 stages of a git change and how do you move a file from one stage to the other?
  1.  add
  2.  commit
  3.  push
* Write a handy cheatsheet of the commands you need to commit your changes?
  * branch
  * commit
  * add
  * push
* What is a pull request and how do you create and merge one?
  * A pull request is a set of changes from a branch.  
* Why are pull requests preferred when working with teams?
  * Pull requests are a form of better change control.  This is much preferred to pushing changes directly to the master branch.

Add response to reflection questions
Add response to reflection questions
