Skip to content
GitTree
العربية

Video: Read history without moving HEAD

The video plays in YouTube’s player, in privacy-enhanced mode.

Record the leftover radius edit, document the actual history, and compare revision sets with file-tree differences. Selecting a graph row is inspection, not a branch switch.

Read the full lesson

The article has every step and command from the video, the practice exercise and the questions.

Go to the lesson

Video transcript

The narration of the video, cue by cue.

  1. Read history without moving your current branch.
  2. First inspect the one independent edit left by L007.
  3. Record the radius as its own local commit.
  4. Write the documented chain using subjects, not invented hashes.
  5. The document becomes the fifth commit in this chain.
  6. Verify the actual order before teaching revision notation.
  7. A branch name and a selected graph row are different.
  8. Selecting the root only changes the inspected commit.
  9. The full tree is not just the list changed in that commit.
  10. Search the loaded history, not a promised server-wide archive.
  11. Return the selection to the current tip.
  12. The terminal independently confirms the checked-out branch.
  13. Two parent steps are not the second parent of one commit.
  14. This non-merge commit has no second parent.
  15. These sets agree here because the endpoints are ancestors.
  16. A tree difference names files, not a set of commit identities.
  17. Use a measured commit ID in the comparison picker.
  18. Compare the two resolved trees without changing refs.
  19. This mode compares the merge base with the right side.
  20. A diverged graph makes the two log ranges differ.
  21. Three-dot log and three-dot diff answer different questions.
  22. A mistaken selection needs navigation, not destructive recovery.
  23. Verify the chain and unchanged HEAD before branching.
  24. Next, create and switch branch names deliberately.

All tutorials