Part 3: Version Control (Git) [10 points]

`1In order to practice utilizing Git in a collaborative environment, you must first get used to utilizing the functionality when programming on your own. The benefits of version control even when programming individually are immense. At inception, ensure that you push your program project files onto your remote repository. $git add filename.extension (adding project files to the staging area) $git commit mcommitting the program project files filename.extension $git push origin (now your local files which you committed are in your remote repository, you now have a local copy and a backup just in case on your GitHub repository).

Now that you have a remote central repository, create a branch so that you have a stable version of the code to go back to incase anything goes wrong. $git branch testing (this creates a branch, which is basically a copy of your code, you may edit the code, test it and if it is stable push it to your remote repository). $git checkout testing (switching to the testing branch) If you have completed a significant amount of programming, and you believe you have tested it sufficiently and it is stable you can push to the central repository on GitHub. $git push u origin testing I expect you to use Git throughout the development process, and to submit a screenshot of your commit logs utilizing the Git log command ($git log).