🔀 Git & GitHub

What you can learn on this page

• 🎯 What are Git and GitHub? — Git is like a medical record system for your project: every meaningful change is written down with a timestamp, a doctor's signature, and a reason — not just the final diagnosis but the entire history of how the patient arrived there. But here is the real ques
• ⚙️ Installation and First Configuration — Installing Git is like registering as an official contractor before stepping onto a building site: the gate logs your badge number, your name, and which door you entered — every nail you hammer is traceable to you. The question to sit with before moving to com
• ⌨️ Git Basics: status, add, commit, diff, log — The staging area works exactly like a shopping cart that sits between the store shelves and the checkout counter: you can put things in the cart, take them out, swap them — and the receipt is only printed when you actually check out. The "why" worth
• 🚫 .gitignore: Keep the Right Files Out of Git — .gitignore works like the "do not publish" stamp a legal team puts on internal draft documents before sending a contract packet to the client: the drafts still exist in the office filing cabinet, they just never leave the building. The critical "
• 🌿 Branch & Switch: Create, Rename and Shelve Work — A Git branch is like a parallel universe copy of your codebase that costs nothing to create — you are not duplicating files, you are only moving a pointer one step sideways, the same way a train switches track without physically duplicating the train. The thou
• 🔀 Merge & Conflict: Bring Changes Together Safely — A Git merge is like a court stenographer reconciling two witnesses' testimony of the same event: wherever their stories don't overlap, Git combines them automatically, but the moment two people changed the exact same line, it stops guessing and hands you the c
• 🧬 Rebase & Advanced Flow: Cherry-pick and Rewriting History — Rebase and cherry-pick are both time-machine tools that rewrite WHERE a commit sits in history, but they answer two different questions: rebase asks "what if my whole branch had started from a later point in time?" and replays every one of your commi
• 🐙 GitHub Workflow: Repository, Remote, Pull Request, Review — GitHub is the air traffic control tower for your team's code: every pilot (developer) has their own runway (branch), but before any plane lands on the main runway (main), the tower approves the flight path, checks for conflicts with other aircraft, and only th