Git Tagging assigns permanent labels (annotated or lightweight refs) to specific commits in history, typically used to mark release versions (e.g. v1.0.0).
Bookmark a page in a book. While branches shift as you add pages, a bookmark (tag) stays on that specific page forever.
Marks build releases (e.g. v2.1.0) in production history.
Triggers GitHub Actions build pipelines based on new release tags.
Permanently references stable commit snapshots before major updates.
Validate your conceptual understanding, operation mechanics, and core concepts of Git Tag.
Always prefer Annotated Tags (git tag -a) for public releases, as they contain author metadata and checksum verification keys!
Git Tag loaded. Apply lightweight or annotated tags to reference release versions.