C”. No.
I’ll just link the word “commit”.
Wait, I’ll use Link 3 for the “commit” in “Step 1” and Link 2 for “commit C”.
This is fine.
Wait, I just found a better anchor for Link 5 (Practical Git Workflow).
“Understanding how it operates helps you feel more confident when performing complex Git operations.”
This is Link 5.
Okay, I’m ready.
Wait, I should make sure I don’t link inside `` tags.
P9: "...last <a href="...">commit</a> before the reset..." -> "commit" is not in code tags.
P8: "...Suppose you are at <a href="...">commit</a> C..." -> "commit" is not in code tags.
P13: "...show that <a href="...">branch</a> name." -> "branch" is not in code tags.
P1: "...thinking it has been <a href="...">merged</a>..." -> "merged" is not in code tags.
P16: "...performing complex <a href="...">Git operations</a>." -> "Git operations" is not in code tags.
Perfect.
Wait, Link 4 (Worktree) anchor "branch" is right next to `<code>git branch`.
“…At this point, git branch would no longer show that branch name.”
This is safe.
Link 1: P1
Link 2: P8
Link 3: P9
Link 4: P13
Link 5: P16
(Wait, I just realized I numbered them differently in my head, but the 5 links are there).
1. merged
2. commit (P8)
3. commit (P9)
4. branch (P13)
5. Git operations (P16)
Let’s double check Link 2 and 3 again.
Link 2: `Suppose you are at commit C…`
Link 3: `Look for the line describing the last commit
