Iterating on Feedback
Real feedback landed on YOUR OWN PR this time. Two real, genuinely different ways to respond to it.
The simplest, most common real way to update a PR is exactly what it sounds like: push another commit. GitHub (and this real branch) picks it up automatically — no special command needed, no re-opening anything.\n\nBut real work is rarely perfect the first time. A genuine typo, caught immediately, is the exact real scenario git commit --fixup exists for: mark a new commit as "this really belongs squashed into that earlier one," then git rebase -i --autosquash folds it in automatically — producing exactly the clean, real history a PR deserves before it merges, without ever needing to replay the branch's own real merge commit.
Reading Real Feedback on Your Own PR
git notes show HEAD
The Simplest Real Response: Just Push Another Commit
# edit the file to address the real feedback
git add creme-brulee.md
git commit -m "Add serving size to creme brulee recipe"
No special ceremony — a PR updates the instant a new commit lands on its branch.
A Real Typo, Caught Immediately
git commit -m "Note leftover storage for creme brulee"
# ...typo spotted: "2 dyas"
Cleaning It Up Before Merge
git commit --fixup=<hash of the typo'd commit>
git rebase -i --autosquash <the branch's own merge commit>
--autosquash automatically reorders the fixup right after its real target and folds it in — one clean, real commit, exactly as if the typo had never happened. Scoping the rebase to start right after the branch's own merge commit means that real merge is never touched or replayed.
git commit --fixup=<commit>
Creates a real new commit explicitly marked as belonging squashed into an earlier, specific commit — confirmed directly in this lab by its real, distinctive "fixup!" message prefix.
git rebase -i --autosquash
Automatically reorders any real fixup! commits directly after their real target and folds each one in during the rebase — confirmed directly in this lab: no manual reordering needed, the messy history from that automatically becomes one clean, real commit.
📖 Read the Real Feedback
A teammate left a genuine review note directly on your PR's tip commit.
cd ~/team-recipes && git notes show HEADstudent@lab:~$ cd ~/team-recipes && git notes show HEAD Great additions! Could you note the serving size on the creme brulee recipe before we merge?
✏️ Respond the Simplest Real Way
Just push another commit — a PR updates automatically, no special ceremony required.
cd ~/team-recipes && printf '\nServes 6.\n' >> creme-brulee.mdcd ~/team-recipes && git add creme-brulee.mdcd ~/team-recipes && git commit -m 'Add serving size to creme brulee recipe'student@lab:~$ cd ~/team-recipes && printf '\nServes 6.\n' >> creme-brulee.md student@lab:~$ cd ~/team-recipes && git add creme-brulee.md student@lab:~$ cd ~/team-recipes && git commit -m 'Add serving size to creme brulee recipe' [feature/dessert-menu 5f8fbb9] Add serving size to creme brulee recipe 1 file changed, 2 insertions(+)
🩹 Catch a Real Typo, Fix It With --fixup
One more real note is added — but this one has a genuine typo. Mark the fix as belonging squashed into it.
cd ~/team-recipes && printf 'Store leftovers in the fridge for up to 2 dyas.\n' >> creme-brulee.mdcd ~/team-recipes && git add creme-brulee.mdcd ~/team-recipes && git commit -m 'Note leftover storage for creme brulee'cd ~/team-recipes && sed -i 's/2 dyas/2 days/' creme-brulee.mdcd ~/team-recipes && git add creme-brulee.mdcd ~/team-recipes && git commit --fixup=HEADstudent@lab:~$ cd ~/team-recipes && printf 'Store leftovers in the fridge for up to 2 dyas.\n' >> creme-brulee.md student@lab:~$ cd ~/team-recipes && git add creme-brulee.md student@lab:~$ cd ~/team-recipes && git commit -m 'Note leftover storage for creme brulee' [feature/dessert-menu 89c94d2] Note leftover storage for creme brulee 1 file changed, 1 insertion(+) student@lab:~$ cd ~/team-recipes && sed -i 's/2 dyas/2 days/' creme-brulee.md student@lab:~$ cd ~/team-recipes && git add creme-brulee.md student@lab:~$ cd ~/team-recipes && git commit --fixup=HEAD [feature/dessert-menu 7733079] fixup! Note leftover storage for creme brulee 1 file changed, 1 insertion(+), 1 deletion(-)
🧹 Fold It In and Push the Clean History
Autosquash the fixup into its real target, safely scoped to never touch the branch's own merge commit.
cd ~/team-recipes && git rebase -i --autosquash be669152c10e6f9ad36db024e7d0efe451302499cd ~/team-recipes && git log --oneline -3cd ~/team-recipes && cat creme-brulee.mdcd ~/team-recipes && git pushstudent@lab:~$ cd ~/team-recipes && git rebase -i --autosquash be669152c10e6f9ad36db024e7d0efe451302499 Successfully rebased and updated refs/heads/feature/dessert-menu. student@lab:~$ cd ~/team-recipes && git log --oneline -3 c6a0e6b (HEAD -> feature/dessert-menu) Note leftover storage for creme brulee 5f8fbb9 Add serving size to creme brulee recipe be66915 (origin/feature/dessert-menu) Merge remote-tracking branch 'origin/master' into feature/dessert-menu student@lab:~$ cd ~/team-recipes && cat creme-brulee.md Creme Brulee Bake custard in a water bath, torch sugar topping before serving. Serves 6. Store leftovers in the fridge for up to 2 days. student@lab:~$ cd ~/team-recipes && git push Enumerating objects: 8, done. Counting objects: 100% (8/8), done. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 640 bytes | 71.00 KiB/s, done. Total 6 (delta 3), reused 0 (delta 0), pack-reused 0 To ../recipes-origin.git be66915..c6a0e6b feature/dessert-menu -> feature/dessert-menu
Lab 2.5.3 complete. Real feedback, addressed two genuinely different real ways:\n\n\n Feedback read : ✅ git notes show\n Simplest response : ✅ plain new commit\n Real typo caught+fixed : ✅ --fixup\n History cleaned up : ✅ --autosquash, merge untouched\n
Enable JavaScript to run the live terminal and track your progress.