Skip to content
GitTree
العربية

Video: Push commits and publish a branch

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

Publish the intended branch to the local bare origin without overwriting Leo's newer main. Bring the behind-only main forward explicitly, then publish the feature with its own upstream.

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. Start from the exact checkpoint.
  2. Name the branch, index and working version.
  3. Prepare only the isolated course copy.
  4. Inspect the exact source and destination.
  5. Fast-forward only when the ancestry allows it.
  6. Stop if the actual branches have diverged.
  7. Main already matches the destination now.
  8. Publish the named feature, not every branch.
  9. Verify the feature's own upstream.
  10. Publication does not merge the feature.
  11. Leave the original main clean.
  12. What does publishing F1 do?
  13. It sends that named ref, not all working files.
  14. Which facts hold after canonical success?
  15. Its push was already aligned.
  16. Fast-forward main/H6 to descendant H7: new merge commit?
  17. The ref moves to an existing descendant.
  18. Change input: push old H6 over server H7 before alignment.
  19. The native take exited1, preserving H7.
  20. Push says already up to date. Is F1 published?
  21. Main's result says nothing about another ref.
  22. Which final evidence is needed?
  23. Compare actual SHAs for each branch.
  24. Verify the actual result, not just a message.
  25. Predict the changed input before acting.
  26. Preserve useful work before recovery.
  27. Prove the checkpoint before continuing.
  28. Keep the verified result for the next step.

All tutorials