In previous lessons, we learned about the key aspects of the Git workflow: make changes -> stage changes -> commit changes This basic workflow is appropriate in many circumstances. However, there are situations where you want to keep a working version of your project and make changes to your files. This is where Git branches come in! Why we need

I hope that you have been following these lessons and found them useful. One of the key things about learning Git is that you have to use it regularly in order to remember the names of the various commands you use most often. Also, the more you use Git, the more you will start to think about your documents and

Moving on from the previous lesson, you will now learn how to view the differences between files in your repository. More appropriately, you will learn to view the differences between one version of the files in your repository and another version of the files in your repository. As you get more familiar with Git, you will find yourself using this

Great work! In the last lesson you learned to use git add <filename> to add a file to the staging area of your repository, and then git commit to permanently save these changes. That cycle – make changes, add changes, commit changes – is fundamental to the Git workflow and we will revisit it several more times over the course