Git Tag
A Git tag is a name that points to one exact object, often a release commit. An annotated tag can also store who made it, a message, a date, and a signature.
Another example
Version 3.2.0 is ready at a verified commit. A signed annotated tag named v3.2.0 points to it and is pushed on purpose. Moving a published release tag breaks the source record other people rely on.
Main parts
- 01tag name
- 02target object
- 03annotation or signature
Use it when
Use this term when giving one exact commit or release point a stable name.
Do not use it when
Do not treat a simple local tag as a full release record, and do not secretly move a published tag.
Name used in code
git tag -s v3.2.0 <commit> Before you ship
Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback.
Outcome: Use Git Tag to release or recover the change safely, with a clear record. User context: Version 3.2.0 is ready at a verified commit. A signed annotated tag named v3.2.0 points to it and is pushed on purpose. Moving a published release tag breaks the source record other people rely on. Delivery concept or operation: Git Tag. Why it fits: Use this term when giving one exact commit or release point a stable name. Do not use it when: Do not treat a simple local tag as a full release record, and do not secretly move a published tag. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.
Check this request
Review the current use of Git Tag. Definition: A Git tag is a name that points to one exact object, often a release commit. An annotated tag can also store who made it, a message, a date, and a signature. Release checks: Before publishing, check the exact repository, branch, target, and diff. Keep unpublished work. Pass review and CI checks. Record conflict and data-loss risks, release order, traceability, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.