Bird
Raised Fist0
Gitdevops~10 mins

Semantic versioning with tags in Git - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the command to create a new Git tag named v1.0.0.

Git
git tag [1]
Drag options to blanks, or click blank then click option'
Aversion1
Bv1.0.0
Crelease
Dtag1
Attempts:
3 left
💡 Hint
Common Mistakes
Using tag names without the 'v' prefix.
Using non-numeric or unclear tag names.
2fill in blank
medium

Complete the command to push the tag v2.1.0 to the remote repository.

Git
git push origin [1]
Drag options to blanks, or click blank then click option'
Av2.1.0
Bdevelop
Cmain
Dmaster
Attempts:
3 left
💡 Hint
Common Mistakes
Pushing a branch name instead of a tag.
Forgetting to push tags after creating them.
3fill in blank
hard

Fix the error in the command to list all tags sorted by version.

Git
git tag --sort=[1]
Drag options to blanks, or click blank then click option'
Acommitterdate
Bdate
Cname
Dversion
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'date' or 'name' which do not sort by semantic version.
Misspelling the sort option.
4fill in blank
hard

Fill both blanks to create an annotated tag with message 'Release 3.0.0'.

Git
git tag -a [1] -m [2]
Drag options to blanks, or click blank then click option'
Av3.0.0
B"Release 3.0.0"
C"Release 3.0"
Dv3
Attempts:
3 left
💡 Hint
Common Mistakes
Using lightweight tags without messages.
Forgetting quotes around the message.
5fill in blank
hard

Fill all three blanks to delete a local tag and then delete it from the remote.

Git
git tag -d [1] && git push origin :refs/tags/[2] && git fetch --prune origin [3]
Drag options to blanks, or click blank then click option'
Av1.2.3
Bv2.0.0
Dv3.0.0
Attempts:
3 left
💡 Hint
Common Mistakes
Using different tag names in each command.
Forgetting to delete the tag remotely.

Practice

(1/5)
1. What does the PATCH number represent in semantic versioning like 1.4.2?
easy
A. Build metadata or pre-release information
B. New features added in a backward-compatible way
C. Major changes that break backward compatibility
D. Bug fixes and small changes that do not affect the API

Solution

  1. Step 1: Understand semantic versioning parts

    Semantic versioning uses MAJOR.MINOR.PATCH format where PATCH is the last number.
  2. Step 2: Identify PATCH meaning

    PATCH is for bug fixes or small improvements that do not change the API or features.
  3. Final Answer:

    Bug fixes and small changes that do not affect the API -> Option D
  4. Quick Check:

    PATCH = bug fixes [OK]
Hint: PATCH fixes bugs without changing features [OK]
Common Mistakes:
  • Confusing PATCH with MINOR or MAJOR
  • Thinking PATCH adds new features
  • Mixing PATCH with build metadata
2. Which git command correctly creates an annotated tag named v2.1.0 with a message?
easy
A. git tag -a v2.1.0 -m "Release version 2.1.0"
B. git tag v2.1.0 -m "Release version 2.1.0"
C. git tag -m "Release version 2.1.0" v2.1.0
D. git tag --message v2.1.0 "Release version 2.1.0"

Solution

  1. Step 1: Recall annotated tag syntax

    Annotated tags use -a and -m for message: git tag -a tagname -m "message".
  2. Step 2: Match correct command

    git tag -a v2.1.0 -m "Release version 2.1.0" matches this syntax exactly, others misuse flags or order.
  3. Final Answer:

    git tag -a v2.1.0 -m "Release version 2.1.0" -> Option A
  4. Quick Check:

    Annotated tag = git tag -a -m [OK]
Hint: Use -a and -m together for annotated tags [OK]
Common Mistakes:
  • Omitting -a for annotated tags
  • Placing -m before tag name incorrectly
  • Using --message instead of -m
3. Given these git tags: v1.0.0, v1.2.0, v1.2.3, what will git describe --tags output if the current commit is exactly at v1.2.3?
medium
A. v1.2.3
B. v1.2.3-0-g
C. v1.2.0
D. v1.2.3-1-g

Solution

  1. Step 1: Understand git describe output

    If the current commit matches a tag exactly, git describe --tags outputs just that tag name.
  2. Step 2: Apply to given tags

    Since current commit is exactly at v1.2.3, output is v1.2.3 without extra suffix.
  3. Final Answer:

    v1.2.3 -> Option A
  4. Quick Check:

    Exact tag commit = tag name only [OK]
Hint: Exact tag commit shows tag name only [OK]
Common Mistakes:
  • Expecting extra suffix even on exact tag
  • Confusing closest previous tag with current
  • Misunderstanding commit hash suffix
4. You tried to create an annotated tag with git tag -m "Release 1.0" v1.0.0 but it created a lightweight tag instead. What is the error?
medium
A. Using double quotes instead of single quotes for message
B. Incorrect order of arguments; message must come after tag name
C. Missing -a flag to create an annotated tag
D. Tag name v1.0.0 is invalid

Solution

  1. Step 1: Check command syntax for annotated tags

    Annotated tags require -a flag; -m alone creates lightweight tag with message ignored.
  2. Step 2: Identify missing flag

    The command lacks -a, so it made a lightweight tag instead of annotated.
  3. Final Answer:

    Missing -a flag to create an annotated tag -> Option C
  4. Quick Check:

    Annotated tag needs -a flag [OK]
Hint: Always use -a for annotated tags [OK]
Common Mistakes:
  • Omitting -a flag
  • Thinking -m alone creates annotated tag
  • Confusing argument order
5. You want to tag a release as v3.0.0 but only if the current commit is ahead of v2.9.9 by at least one commit. Which sequence of commands correctly checks this and creates an annotated tag if true?
hard
A. git describe --tags --match "v2.9.9" && git tag -a v3.0.0 -m "Release v3.0.0"
B. if [ $(git rev-list v2.9.9..HEAD --count) -gt 0 ]; then git tag -a v3.0.0 -m "Release v3.0.0"; fi
C. git tag -a v3.0.0 -m "Release v3.0.0" && git rev-list v2.9.9..HEAD --count
D. git tag v3.0.0 && git rev-list --count v2.9.9..HEAD

Solution

  1. Step 1: Check commits ahead of v2.9.9

    Use git rev-list v2.9.9..HEAD --count to count commits ahead.
  2. Step 2: Conditional tag creation

    If count is greater than 0, create annotated tag with git tag -a v3.0.0 -m "Release v3.0.0".
  3. Final Answer:

    if [ $(git rev-list v2.9.9..HEAD --count) -gt 0 ]; then git tag -a v3.0.0 -m "Release v3.0.0"; fi -> Option B
  4. Quick Check:

    Count commits then tag if ahead [OK]
Hint: Count commits ahead before tagging [OK]
Common Mistakes:
  • Tagging without checking commit count
  • Using git describe incorrectly for this check
  • Creating lightweight tag instead of annotated