1. Lightweight tag
git tag <name> creates a lightweight tag — just a name pointing at the current commit.
git tag v1.0.0Typorithm · medium
Step 1 of 8 · intro card
Remote & Collab
A lightweight tag names a commit; an annotated tag (-a) stores a message, author, and date and is preferred for releases. Tags are not pushed by default — push them explicitly or with --tags. git describe names a commit relative to the nearest tag.
git tag v1.0.0 creates a lightweight tag — a simple, permanent name for a commit, often a release point in semver form (major.minor.patch).
git tag -a v1.1.0 -m "release" creates an annotated tag, which stores a message, the tagger's name, and a date. Annotated tags are the recommended form for published releases.
Tags are not sent on a normal push. You push one with git push origin <tag> or all of them with git push --tags. git describe --tags then names any commit relative to the most recent tag, like v1.1.0-3-gabc123.
Lightweight tag = a name for a commit.
Annotated tag (-a) stores message, author, and date.
Tags are not pushed by default — use --tags or name one.
git tag v1.0.0
git tag -a v1.1.0 -m "release"
git push origin v1.0.0
git push --tags
git describe --tagsConnect each part of the code to the concept before you type.
git tag <name> creates a lightweight tag — just a name pointing at the current commit.
git tag v1.0.0-a creates an annotated tag storing a message, author, and date — preferred for releases.
git tag -a v1.1.0 -m "release"Tags are not pushed by default; naming the tag pushes just that one to origin.
git push origin v1.0.0--tags pushes every local tag to the remote at once.
git push --tagsgit describe names the current commit relative to the nearest tag.
git describe --tagsRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.