Git rebase is a Git command used to move or reapply commits from one branch onto another base commit, creating a clean, linear commit history.
🔹 What Rebase Does (Conceptually)
Instead of merging branches with a merge commit, rebase rewrites commit history.
Before rebase
main: A ── B ── C
feature: └── D ── E
After rebase
main: A ── B ── C ── D' ── E'
(D and E are replayed on top of C)
🔹 Why Use Git Rebase?
✔ Keeps history linear and clean
✔ Avoids unnecessary merge commits
✔ Easier to read project history
✔ Useful before merging feature branches
✅ Basic Rebase Command
git checkout feature
git rebase main
🔹 Interactive Rebase (Most Powerful)
git rebase -i HEAD~3
Used to:
- Squash commits
- Reorder commits
- Edit commit messages
- Remove commits
⚠️ Important Warning (Interview Favorite)
❌ Never rebase public/shared branches
✔ Rebase only local or feature branches
Because rebase rewrites commit history.
🆚 Rebase vs Merge (Quick Comparison)
| Rebase | Merge |
|---|---|
| Linear history | Preserves full history |
| Rewrites commits | Creates merge commit |
| Cleaner log | Shows branch structure |
| Risky on shared branches | Safe everywhere |
🎯 Short Interview Answer
Git rebase is used to move a branch’s commits onto another base commit, creating a linear and clean commit history. It rewrites history and should only be used on local or feature branches.
⭐ One-line summary
Rebase rewrites history to make commits look like they were made sequentially.
