Skip to content
GitTree
العربية

Video: Connect a remote without confusing it with an upstream

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

Add a local bare origin, fetch its main branch and deliberately choose what local main tracks. Prove that a remote name, a remote-tracking ref and an upstream setting are three different things.

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. Connect a remote, then choose an upstream deliberately.
  2. The feature exists locally; it has not been published.
  3. Disable background fetching only in this recording repository.
  4. Switch to main before writing the transport document.
  5. Save the complete document without machine-specific paths or credentials.
  6. Stage the transport document on main, not on the feature.
  7. The document adds the sixth commit on main.
  8. Prepare a separate bare copy of main for local transport.
  9. This destination has main, but no feature branch.
  10. The original and bare destination are separate repositories.
  11. Generate a file URL for the intended local destination.
  12. Saving the address does not fetch branches or upload the feature.
  13. Open the remote dialog in the original repository.
  14. Name it origin and verify the complete destination.
  15. The remote is configured; its branch has not been fetched.
  16. The fetch rule exists while the tracking-ref query is empty.
  17. Selecting a missing upstream fails without moving main.
  18. Does choosing an upstream replace fetching? It does not.
  19. Fetch the remote's main without switching your current branch.
  20. Origin slash main is your local fetched record.
  21. Fetching is not merging, rebasing or replacing the page.
  22. Choose the relationship for the named local main branch.
  23. Selecting the option alone is not the confirmed relationship.
  24. Confirm main's upstream without moving its commit.
  25. Verify main, its upstream, matching tips and clean work.
  26. An empty server feature query does not mean the local feature was lost.
  27. Address, fetched record and upstream setting remain different things.
  28. Correct an upstream choice without resetting the history.
  29. Verify the original and server separately before continuing.
  30. Explain why the missing ref required a fetch, not a push.
  31. A local bare remote is not a hosted project or a pipeline.
  32. Next, fetch a teammate's update while keeping your own files unchanged.

All tutorials