BitWithBiteGit & GitHub · Quick Reference
Lesson 6 — GitHub Workflow Cheat Sheet
In one line: GitHub Flow is a lightweight, branch-based workflow that teams use everywhere from startups to Fortune 500 companies. It has one rule: main is always deployable. All work happen...
Key Ideas
1GitHub Flow — The Industry Standard. GitHub Flow is a lightweight, branch-based workflow that teams use everywhere from startups to Fortune 500 companies. It has one rule: main is always deployable. All w...
2Creating Pull Requests. A Pull Request (PR) is a formal request to merge your branch into another (usually main). It's where code review happens — teammates can see exactly what changed, comm...
3Code Review. Code review is one of the most valuable practices in software development. It catches bugs before production, spreads knowledge through the team, and maintains code qu...
4Forking Repositories. Forking creates your own copy of someone else's repository on GitHub. Unlike cloning (which just downloads), a fork is a full GitHub repo under your account that you c...
5GitHub Issues. GitHub Issues are the task tracker built into every repository. Use them to report bugs, request features, ask questions, or plan work. Issues integrate tightly with P...
Code Examples
# 1. Start from latest main
git switch main
git pull origin main
# 2. Create your feature branch
git switch -c feat/user-auth
# 3. Make commits as you work
git add .
git commit -m "feat: add JWT authentication middleware"
# 4. Push your branch to GitHub
...
# 1. Fork on GitHub (click the Fork button on the repo page)
# This creates: github.com/YOUR_USERNAME/original-repo
# 2. Clone YOUR fork (not the original)
git clone git@github.com:YOUR_USERNAME/original-repo.git
cd original-repo
# 3. Add the original ...
### Option 1: Merge approach (simpler)
git switch feat/my-feature
git fetch origin
git merge origin/main
# Resolve any conflicts in your editor
git add .
git commit -m "merge: sync with main"
git push
### Option 2: Rebase approach (cleaner history)
git swi...