Skip to content
GitTree
العربية

Video: Fetch a teammate's change without replacing your page

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

Receive Leo's real footer commit while keeping main, the index and the original working page unchanged. Then inspect stale-ref pruning in a separate replay so server deletion is not confused with local cleanup.

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. Receive the update without replacing your current page.
  2. Keep background fetching off for this before-and-after take.
  3. Prepare Leo's separate clone with a fictional local identity.
  4. Leo records and pushes the footer reminder to the local origin.
  5. The server moved while your fetched record stayed behind.
  6. These counts use your local fetched ref, not a live server snapshot.
  7. Which ref will move, and which file version will stay?
  8. Fetch all configured remotes; here there is only origin.
  9. Wait for Git's result before treating the update as received.
  10. Selecting Leo's commit does not check it out.
  11. Compare main with the fetched tree without moving either ref.
  12. The fetched tree has the reminder; your working page still does not.
  13. The original working file keeps its old footer.
  14. Clean working changes do not mean your branch is up to date.
  15. Verify six local commits, seven fetched commits and one behind.
  16. Fetching updated knowledge without integrating the file contents.
  17. A local edit in the same file survives this fetch.
  18. The server branch is already gone before this pruning example.
  19. Preview the stale tracking ref before removing it.
  20. Remove the stale local tracking ref, not the local rescue branch.
  21. The local branch and working page remain intact.
  22. A prior fetch may already have removed the stale tracking ref.
  23. Keep the original clean and behind one; do not pull or force-push.
  24. Next, inspect the destination before publishing a branch.

All tutorials