← Course
Git & GitHub for Beginners
The missing piece that ties every curriculum together. In the real world Git isn’t optional—it’s required. Focus on workflow, not memorising commands: safe local history, push to GitHub, branching, pull requests, and .gitignore.
GitGitHubLast updated 3 Feb 2026
Level 1: Solo Player (Securing Your Own Code)
Focus on recording changes on your local machine.
Session 1: Intro & Installation
- What is Git? The “save point” analogy from video games.
- Setup: install Git and configure user.name and user.email.
- Create your first repo with git init.
Session 2: The Three Musketeers (Add, Commit, Log)
- Working directory, staging area, and repository: how your code moves between them.
- git add: choose which files to save.
- git commit -m: write clear, descriptive change messages.
- git log: view the history of what you’ve done.
Session 3: Time Travel (Undoing Mistakes)
- git checkout or git restore: go back to an older version when something breaks.
- git diff: see exactly what you’ve changed before committing.
Level 2: Going Cloud (GitHub & Portfolio)
Store code on the internet so it’s safe and shareable.
Session 4: GitHub Basics
- Create a GitHub account and set up SSH key or Personal Access Token (secure access).
- Connect your local folder to the cloud with git remote add.
- git push: send your code to GitHub.
Session 5: Cloning & Pulling
- git clone: download someone else’s project (or your own from another machine) to your laptop.
- git pull: update your local copy when there are new changes on GitHub.
Level 3: Team Player (Collaboration Without Clashes)
Learn to work in a team without overwriting each other’s work.
Session 6: Branching (Parallel Tracks)
- git branch: create a separate line of work (e.g. one for a Login feature, one for Register).
- git merge: bring a finished feature back into main.
Session 7: Pull Requests & Conflict
- How to open a Pull Request (PR) on GitHub (industry standard).
- Merge conflicts: how to calmly fix the situation when two people change the same lines.
Level 4: Professional Habits
Session 8: Ignoring Files (.gitignore)
- Why node_modules, vendor, or secret files like .env must not be committed.
- Writing a proper .gitignore file.
Session 9: GitHub Pages (Deployment)
- Turn a GitHub repository into a public website for free (ideal for HTML/CSS/JS projects).
- Connect any static site or course project (e.g. from HTML & CSS or JavaScript) so you can share it live.
Interested in this course? I offer mentoring and structured learning—get in touch to discuss your goals.