🔀 Git & GitHub

Learn Git and GitHub with visual workflows, branch strategy, pull requests, GitHub Actions, Pages deployment, safety rules and hands-on command practice.

Learn Git and GitHub visually: snapshots, branches, pull requests, Actions, Pages deployment, production safety rules and hands-on command practice.

What you can learn on this page

  • 🎯 What are Git and GitHub? — Git is like taking labeled photos of your project while you work. If something breaks, you can look at earlier photos, compare what changed, and return to a safe point. GitHub is the shared album where your team reviews, comments, runs checks, and publishes th
  • ⚙️ Installation and First Configuration — Installing Git is like putting a toolbox on your desk. Before building anything, you label the toolbox with your name and email so every saved change is traceable. Before Git commands: understand the terminal tools
  • ⌨️ Git Basics: status, add, commit, diff, log — Staging is like choosing which items go into a delivery box. You may have ten changed files on the table, but only the staged files go into the next commit. Step 4: See Working Tree, Staging Area and Commit
  • 🚫 .gitignore: Keep the Right Files Out of Git — Imagine your desk has a couple of drawers with a sticky note that says "never photograph this drawer." Every time you take a memory-photo of your desk, those drawers are skipped automatically — they still exist, you just never see them in the picture
  • 🌿 Branching, Merge, Rebase and Conflicts — A branch is a safe side road. First watch the road split visually, then watch the roads merge again, then practice what happens when two people edit the same place. 1) Branch creation: main stays safe
  • 🐙 GitHub Workflow: Repository, Remote, Pull Request, Review — GitHub is like the team office for your code. Your branch is your desk, the Pull Request is the meeting table, and main is the approved cabinet. Animate a Real Pull Request Flow
  • 🧾 Pull Request: Open, Review, Approve, Request Changes and Resolve Conflicts — A Pull Request is a controlled discussion before code enters main. It shows the diff, explains the reason, runs checks, collects review decisions and keeps a clear audit trail. GitHub Pull Request screen tour: compare, create, review and merge
  • 🚀 GitHub Actions for QA: CI, Reports, Matrix and Secrets — GitHub Actions is like a factory line. Every time code arrives, machines install dependencies, run tests, build the app and publish reports without asking your laptop. GitHub Actions screen tour: buttons, runs and reports