Skip to content
GitTree
العربية

Video: Tags, annotations and release naming

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

Create an annotated v0.1.0 at the inspected main commit and push only that tag to the local origin. Distinguish a tag object from a branch, signature and hosted release.

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. Choose the exact commit before tagging.
  5. Create an annotated tag at that commit.
  6. Write the name and meaningful annotation.
  7. Annotation does not mean cryptographic signing.
  8. A tag does not switch your branch.
  9. Push only the named tag.
  10. Peel the tag to verify its commit.
  11. Do not invent a hosted release.
  12. What is v0.1.0 here?
  13. The verified object type is tag and it peels to main.
  14. Which claims are justified?
  15. The unsigned annotation adds metadata but does not move HEAD.
  16. Does tagging create another main commit?
  17. The tag ref/object points to an existing commit.
  18. Reuse the same name without force: result?
  19. The measured duplicate attempt exited128 and preserved the tag.
  20. Tag and main IDs differ: corrupt?
  21. An annotated tag's own object differs from its commit target.
  22. What proves the result?
  23. Read both object layers and the actual chosen server ref.
  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