Why Squashing commits in Git? - Purpose & Use Cases

The Big Idea

Discover how one simple step can turn your messy commit history into a story everyone loves to read!

The Scenario

Imagine you have made many small changes in your project and committed each one separately. Now you want to share your work with your team, but the commit history is messy and hard to follow.

The Problem

Manually cleaning up commit history means rewriting each commit one by one, which is slow and confusing. It's easy to make mistakes, lose important changes, or confuse others reviewing your work.

The Solution

Squashing commits lets you combine many small commits into one clear, meaningful commit. This makes your project history neat and easy to understand without losing any work.

Before vs After

✗ Before

git commit -m "fix typo"
git commit -m "update README"
git commit -m "add tests"

✓ After

git rebase -i HEAD~3  # then squash commits into one

What It Enables

It enables a clean, simple project history that everyone can easily read and trust.

Real Life Example

A developer finishes a feature with many small fixes and uses squashing to create one clear commit before merging to the main project branch.

Key Takeaways

Manual commit history can be messy and confusing.

Squashing combines multiple commits into one clean commit.

This makes project history easier to read and maintain.