Typorithm · medium

tags & releases

git-tagsgittagreleasesemver
Saved on this device
Full lesson · 8 learning steps Open any exercise for focused practice
1

Step 1 of 8 · intro card

Learn tags & releases

0%

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.

01

Lightweight tag = a name for a commit.

02

Annotated tag (-a) stores message, author, and date.

03

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 --tags

Read the implementation

Connect each part of the code to the concept before you type.

1. Lightweight tag

git tag <name> creates a lightweight tag — just a name pointing at the current commit.

git tag v1.0.0

2. Annotated tag

-a creates an annotated tag storing a message, author, and date — preferred for releases.

git tag -a v1.1.0 -m "release"

3. Push one tag

Tags are not pushed by default; naming the tag pushes just that one to origin.

git push origin v1.0.0

4. Push all tags

--tags pushes every local tag to the remote at once.

git push --tags

5. Describe commit

git describe names the current commit relative to the nearest tag.

git describe --tags

A complete learning loop

01

Understand

Read the concept map and follow the code breakdown.

02

Reconstruct

Type the implementation, repair mistakes and work through every recall exercise.

03

Verify

Use the final check without hints; revisit weak concepts in short practice sessions.

tags & releases: Lesson & Practice · Typorithm | ApplyDjinn