Why Handling PR feedback and updates in Git? - Purpose & Use Cases

The Big Idea

What if you could fix feedback without juggling emails and lost files?

The Scenario

Imagine you just submitted your code changes to a project and your teammate sends you a list of feedback points. You have to manually find each comment, update your files, and then send a new version by email or chat.

The Problem

This manual way is slow and confusing. You might miss some feedback, accidentally overwrite changes, or create multiple versions that are hard to track. It's easy to lose track of what was fixed and what still needs work.

The Solution

Using Pull Requests (PRs) with git, you can reply directly to feedback, update your code in the same PR, and keep all changes and conversations in one place. This makes collaboration clear, fast, and organized.

Before vs After

✗ Before

Edit files locally
Email updated files
Wait for reply

✓ After

git checkout -b fix-feedback
Make changes
git commit -am 'Address feedback'
git push
Update PR automatically

What It Enables

It enables smooth teamwork where everyone can see progress, discuss changes, and improve code together without confusion.

Real Life Example

A developer submits a PR for a new feature. Reviewers comment on some lines. The developer updates the code in the same PR, and reviewers see the changes instantly, speeding up approval and merging.

Key Takeaways

Manual feedback handling is slow and error-prone.

PRs keep feedback and updates organized in one place.

Collaboration becomes faster and clearer.