Git Rebase Explained

← Back to Git

---

⚡ Git Rebase

git rebase is used to synchronize your current branch with a target branch by moving your commits on top of the target branch's latest commit.

🔄 How it Works

In the current branch, the commits coming from the target branch will be placed below the commits done in the current branch (rewriting history).

Pros: * Reduces merge commits. * Creates a linear, cleaner commit history.

📝 Example

1. Create a branch called feature-1 from dev. Make two commits.

1. Go to dev branch and make two new commits there.

1. Go to feature-1 and rebase dev onto it (bring dev commits below feature-1):

   git rebase dev
   

1. If pushing feature-1 for the first time, use:

   git push origin feature-1
   

   

2. If you have already pushed feature-1 before, you must force push because history was rewritten:

   git push origin feature-1 -f
   

Warning: Use git rebase carefully. It rewrites history, which can cause issues for shared branches.

---

🧠 Quick Quiz — Rebase

#

Why might you need to force push (git push -f) after a rebase?

Because the network connection is slow.

Because you created new files.

Because rebase rewrites the commit history, causing it to diverge from the remote.

You never need to force push.

Rebase creates new commit hashes for the existing commits, so the local history no longer matches the remote history.

---

📝 Want More Practice?

👉 Start Git Advanced Quiz (20 Questions)

---

📬 DevopsPilot Weekly — Learn DevOps, Cloud & Gen AI the simple way.
👉 Subscribe here