Handling PR feedback and updates in Git - Step-by-Step Execution

Process Flow - Handling PR feedback and updates

Create PR

↓

Review Feedback

↓

Make Changes Locally

↓

Commit Changes

↓

Push Updates to PR Branch

↓

PR Updates Reflect in Remote

↓

Repeat Review or Merge

This flow shows how a pull request (PR) is created, reviewed, updated with changes, and finally merged after feedback.

Execution Sample

Git

git checkout -b feature-branch
# make code changes
 git add .
 git commit -m "Fix feedback"
 git push origin feature-branch

This sequence creates a branch, commits changes after feedback, and pushes updates to the remote PR branch.

Process Table

Step	Action	Command	Result
1	Create and switch to new branch	git checkout -b feature-branch	New branch 'feature-branch' created and checked out
2	Make code changes	# edit files locally	Files modified locally
3	Stage changes	git add .	Changes staged for commit
4	Commit changes with message	git commit -m "Fix feedback"	New commit created with message 'Fix feedback'
5	Push branch to remote	git push origin feature-branch	Branch pushed; PR updates with new commit
6	Review updated PR	N/A	Reviewers see updated code in PR
7	Repeat if more feedback	Repeat steps 2-6	Cycle continues until approval
8	Merge PR after approval	git merge feature-branch	Changes merged into main branch

💡 Process stops when PR is approved and merged

Status Tracker

Variable	Start	After Step 1	After Step 4	After Step 5	Final
branch	main	feature-branch	feature-branch	feature-branch	feature-branch merged
commit	commitA	commitA	commitB (fix feedback)	commitB (fix feedback)	commitB merged
remote branch	feature-branch not pushed	feature-branch not pushed	feature-branch not pushed	feature-branch pushed	feature-branch merged

Key Moments - 3 Insights

Why do I need to commit changes before pushing?

You must commit changes locally first (see step 4 in execution_table) because git push only sends committed changes to the remote repository.

What happens if I push without switching to the PR branch?

If you push from the wrong branch, your updates won't appear in the PR (see step 1 and 5). Always confirm you are on the correct branch before pushing.

Can I push multiple commits for one PR update?

Yes, you can commit multiple times locally and push all commits together or separately; the PR will update with all pushed commits (see steps 4 and 5).

Visual Quiz - 3 Questions

Look at the execution_table, what command creates the new commit with feedback changes?

A git add .

B git commit -m "Fix feedback"

C git push origin feature-branch

D git checkout -b feature-branch

💡 Hint

Check step 4 in the execution_table where the commit is created.

At which step does the remote PR branch get updated with your changes?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Result' column in step 5 for when the branch is pushed.

If you forget to switch to 'feature-branch' before pushing, what will happen?

A Your changes push to the wrong branch, PR not updated

B Git will automatically switch branches for you

C Your changes update the PR branch anyway

D Push will fail with an error

💡 Hint

Refer to key_moments about branch switching and step 1 in execution_table.

Concept Snapshot

Handling PR feedback:
1. Create and switch to a feature branch
2. Make and stage changes
3. Commit changes with clear message
4. Push branch to update PR
5. Repeat until approved
6. Merge PR to main branch

Full Transcript

This visual execution shows how to handle pull request feedback using git. First, you create a new branch for your feature or fix. Then you make changes locally and stage them with 'git add'. Next, you commit these changes with a message explaining the update. After that, you push the branch to the remote repository, which updates the pull request with your new commits. Reviewers can then see your changes and provide more feedback if needed. This cycle repeats until the PR is approved and merged into the main branch. Key points include always committing before pushing and ensuring you are on the correct branch to update the PR.