Why Code review in pull requests in Git? - Purpose & Use Cases

The Big Idea

What if you could catch mistakes early and make teamwork feel easy and fun?

The Scenario

Imagine you and your friends are writing a story together by passing a notebook around. Each person writes a part, but you have to wait until the notebook comes back to check if the story makes sense and fix mistakes.

The Problem

This slow back-and-forth makes it easy to miss errors, causes confusion, and wastes time because you can't see changes clearly or discuss them easily.

The Solution

Pull requests let you share your changes online where everyone can see, comment, and suggest improvements before merging. This makes teamwork smooth, clear, and fast.

Before vs After

✗ Before

Email code files back and forth for review

✓ After

Create a pull request on GitHub for team review and discussion

What It Enables

It enables clear, organized, and collaborative code improvements that everyone can track and agree on before changes go live.

Real Life Example

A developer finishes a new feature and opens a pull request so teammates can review the code, suggest fixes, and approve it before adding it to the main project.

Key Takeaways

Manual code sharing is slow and confusing.

Pull requests create a clear space for feedback and teamwork.

This improves code quality and speeds up collaboration.