Lesson 4: GitHub Version Control
Master the essential skills of pushing your code changes to GitHub and managing repository collaboration.
Lesson Objectives
- Push your code to GitHub for version control
- Learn how to share access to your repository with bamarshall06
Watch: GitHub Version Control Tutorial
GitHub Version Control - Notes
Stopping the Flask Server
When Flask is running in the terminal, you need to know how to stop ("kill") it.
On Windows, this is done by pressing:
Ctrl + COnce stopped, the terminal returns to the normal command prompt.
Refreshing the web browser now shows "Site cannot be reached," confirming the server is no longer running.
Preparing to Submit Changes
Open the app folder in Cursor (or your code editor) and check the file changes.
You'll see all the modifications you made in the lesson that have not yet been submitted (committed) to GitHub.
Committing and Pushing to GitHub
In the terminal, instruct Claude (or Git) to send your changes to GitHub.
Git may ask for confirmation before committing.
- Option 1 → Approve one time only.
- Option 2 → Approve and remember for all future commits (recommended if you trust the process).
Once confirmed, the changes are committed and pushed.
Verifying on GitHub
- Log into your GitHub account.
- Refresh the repository page.
- Look for the latest commit message, e.g., "update branding from GCSU to UG."
- Navigate through your repository to confirm changes:
- In
/templates/, the newanimals.htmlpage should now be visible. - Open it in GitHub to confirm it uploaded successfully.
Turning in the Assignment
In your GitHub repository, go to:
Settings → Collaborators
Add the instructor's GitHub username:
bamarshall06Go back to your repository's Code page.
Copy the repository URL (the HTTPS link).
Submit that link as your assignment.
Since the instructor has been added as a collaborator, they can view your code, run the app, and grade your work directly.