Click Here to Return to
Instructions Home Page

How to Commit Code Changes to Your GitHub Repo

It's good practice to commit your changes to your GitHub repo regularly. This allows you to easily "go back" and undo changes when things go wrong. I suggest you commit every time you make something work. It's fast and easy, and it can save you a LOT of pain later on.

Regardless of how often you commit while working on your project, you'll be REQUIRED to commit your changes once you are done with your work and ready to submit your solution.

All commits, both along the way and at the very end of your work, are done the same way. Follow the instructions below which assume that you've already created a VS Code project that is linked to a GitHub repo. This is exactly what you have done if you followed the instructions for getting started with an assignment.

Once you've edited any of your project's files, you'll need to perform the following steps to commit then and sync your work with GitHub:

You can keep repeating this process (edit code, commit/sync your changes) until you've completed your assignment. Once you've done all the work you need to do for an assignment, following the submission instructions included in the assignment description.
Step 1: Visit the "Source Control" tab.
Once you've edited a file in your project and your ready to commit your changes, click on the "Source Control" symbol on the left side of the VS Code window. It looks like some circles connected with lines. It may also have a light blue circle over it showing that VS Code has detected that you have edits that need to be committed. See the screenshot below for an example.
Step 2: Comment and Commit.
You'll now see the Source Control section of the VS Code user interface. It lists the files that have been changed, and has a text box in which you can describe the edits you've made. Add your comments to the "Changes" box as shown in the screenshot below. Then click on the blue Commit button to commit your changes to your repo. The act of "Committing" tells Git that this is a "version" of your file that you want it to remember. Later on, if a future edit messes anything up, you'll be able to easily come back to this version because it was committed to your repo.
Step 3: Save your Modified Files
If you haven't already saved your edited files, VS Code will warn you that you have unsaved changes. Assuming you do want to keep your edits, click "Save All and Commit Changes." If your files have all been saved, you'll not see this option. That's normal and expected!
Step 4: Sync your Committed Changes
The last step is to sync your committed changes with GitHub. This is an important step! Don't forget it! This step takes the changes you've committed locally on your own computer and pushes them to your account on GitHub. You can accomplish this by clicking on the blue "Sync Changes" button which appears after you commit.
SUCCESS! Your edits have been committed to version control, and you've synced your changes with GitHub. If you login to your GitHub account on the github.com website, you should see that the files shown there now have your more recent edits.
Step 5: Continue working on your project.
With your edits committed and synced, you're now ready to start working on the next phase of your project's solution. The Source Control panel should now be empty, reflecting that you no longer have any edits that have not yet been committed to your repo. You can return to the original editor section of VS Code by clicking on the top icon on the left sidebar showing an icon with a stack of files. Click that button to return to the main editor screen of VS Code, as shown in the screenshot below.

Have questions? Post your question to the class discussion forum for the fastest possible help.