Git & Version Control · Question Set

Tags, Releases & Versioning (SemVer) in Git – Git & Version Control interview questions

Tags, Releases & Versioning (SemVer) in Git interview questions for placements and exams.

Subject: Git & Version ControlDifficulty: Mixed13 questions in this set

Set overview

Questions

Included in this set

Subject

Git & Version Control

Explore more sets

Difficulty

Mixed

Level of this set

Git & Version Control – Tags, Releases & Versioning (SemVer) in Git questions (13)

Go through each question and its explanation. Use this set as a focused practice pack for Git & Version Control.

Back to Git & Version Control subject page

1. Which pair correctly deletes a remote tag v1.0.0 from origin after deleting it locally?

Difficulty: MediumType: MCQTopic: Tags

Local delete with `git tag -d`; remote delete with a push of an empty ref to the tag.

2. Why do teams create Git tags and when are annotated tags preferred over lightweight tags?

Difficulty: EasyType: SubjectiveTopic: Tags

Tags mark important points in history (e.g., releases). Annotated tags store metadata (tagger, date, message, signature) and are ideal for official releases; lightweight tags are simple pointers for personal bookmarks.

3. Which command creates an annotated tag named v1.2.0 with a message?

Difficulty: EasyType: MCQTopic: Tags

`-a` creates an annotated tag and `-m` sets its message.

4. How do you push a single tag named v2.0.0 to origin?

Difficulty: MediumType: MCQTopic: Tags

Pushing a specific tag uses `git push <remote> <tag>`; `--tags` pushes all tags.

5. In Semantic Versioning MAJOR.MINOR.PATCH, which increment signals backward-incompatible changes?

Difficulty: EasyType: MCQTopic: SemVer

MAJOR → incompatible, MINOR → new compatible features, PATCH → bug fixes.

6. Which is a valid SemVer pre-release tag?

Difficulty: MediumType: MCQTopic: SemVer

Valid format: MAJOR.MINOR.PATCH-PRERELEASE+BUILD; leading 'v' is not part of SemVer core.

7. What should high-quality release notes include for a tagged release?

Difficulty: MediumType: SubjectiveTopic: Releases

Highlights, breaking changes, migration steps, bug fixes, known issues, contributors, and links to diffs/PRs. Keep crisp and user-centric.

8. Which command creates a GPG-signed tag?

Difficulty: MediumType: MCQTopic: Tags

`-s` signs the tag with your configured GPG key for provenance.

9. How would you design a tagging strategy for a service with weekly releases, hotfixes, and experimental builds?

Difficulty: MediumType: SubjectiveTopic: Tags

Use SemVer for GA (e.g., vX.Y.Z), suffix `-rc.N`/`-beta.N` for candidates, `-hotfix.N` for urgent patches, and build metadata for CI artifacts. Protect tags, sign GA tags, auto-generate notes via CI.

10. Which command lists commits between tags v1.1.0 (exclusive) and v1.2.0 (inclusive) on current branch?

Difficulty: MediumType: MCQTopic: Git Log

`A..B` shows commits reachable from B and not A; `...` is symmetric difference.

11. How do Git hosting releases relate to Git tags, and what extras do they provide?

Difficulty: EasyType: SubjectiveTopic: Releases

A release is metadata built around a tag: rich notes, attachments (artifacts), checksums, and visibility controls—useful for distributing binaries and changelogs.

12. Which command shows the most recent tag reachable from HEAD?

Difficulty: EasyType: MCQTopic: Tags

`git describe` finds the nearest tag; `--abbrev=0` prints only the tag name.

13. You want CI to cut a PATCH release on every merged hotfix PR. Which approach is most appropriate?

Difficulty: MediumType: MCQTopic: Tags

Automate SemVer bumps on protected branch and create annotated (optionally signed) tags with release notes.

More sets in Git & Version Control

Git & Version Control — Fundamentals(14+ Questions)
Git Branching & Collaboration — Core(14+ Questions)
Committing, Staging & History — Essentials(14+ Questions)
Remotes, Sync & Tags — Collaboration Deep Dive(14+ Questions)
Branching Strategies & Merge vs Rebase — History Hygiene(14+ Questions)
Rewriting History Safely — Reset, Revert, Reflog, Restore(14+ Questions)
Branching & Merging Strategies — Merge, Rebase, Fast-Forward(14+ Questions)
Stashing, Cleaning & Working Tree Maintenance(13+ Questions)
Branching Strategies, Pull Requests & Collaboration(13+ Questions)
Rebase, Cherry-pick & History Rewriting (Advanced)(12+ Questions)
Collaboration Workflows, Code Review & Best Practices(14+ Questions)

Explore related subjects

HTML CSS Javascript Typescript SQL & Databases React

Continue your preparation

For complete preparation, combine this set with full subject-wise practice for Git & Version Control. You can also explore other subjects and sets from the links below.

Quick navigation:Git & Version Control subject page•All subjects

Subject page

Git & Version Control · Question Set

Tags, Releases & Versioning (SemVer) in Git – Git & Version Control interview questions

Tags, Releases & Versioning (SemVer) in Git interview questions for placements and exams.

Subject: Git & Version ControlDifficulty: Mixed13 questions in this set

Set overview

Questions

Included in this set

Subject

Git & Version Control

Explore more sets

Difficulty

Mixed

Level of this set

Git & Version Control – Tags, Releases & Versioning (SemVer) in Git questions (13)

Go through each question and its explanation. Use this set as a focused practice pack for Git & Version Control.

Back to Git & Version Control subject page

1. Which pair correctly deletes a remote tag v1.0.0 from origin after deleting it locally?

Difficulty: MediumType: MCQTopic: Tags

Local delete with `git tag -d`; remote delete with a push of an empty ref to the tag.

2. Why do teams create Git tags and when are annotated tags preferred over lightweight tags?

Difficulty: EasyType: SubjectiveTopic: Tags

3. Which command creates an annotated tag named v1.2.0 with a message?

Difficulty: EasyType: MCQTopic: Tags

`-a` creates an annotated tag and `-m` sets its message.

4. How do you push a single tag named v2.0.0 to origin?

Difficulty: MediumType: MCQTopic: Tags

Pushing a specific tag uses `git push <remote> <tag>`; `--tags` pushes all tags.

5. In Semantic Versioning MAJOR.MINOR.PATCH, which increment signals backward-incompatible changes?

Difficulty: EasyType: MCQTopic: SemVer

MAJOR → incompatible, MINOR → new compatible features, PATCH → bug fixes.

6. Which is a valid SemVer pre-release tag?

Difficulty: MediumType: MCQTopic: SemVer

Valid format: MAJOR.MINOR.PATCH-PRERELEASE+BUILD; leading 'v' is not part of SemVer core.

7. What should high-quality release notes include for a tagged release?

Difficulty: MediumType: SubjectiveTopic: Releases

Highlights, breaking changes, migration steps, bug fixes, known issues, contributors, and links to diffs/PRs. Keep crisp and user-centric.

8. Which command creates a GPG-signed tag?

Difficulty: MediumType: MCQTopic: Tags

`-s` signs the tag with your configured GPG key for provenance.

9. How would you design a tagging strategy for a service with weekly releases, hotfixes, and experimental builds?

Difficulty: MediumType: SubjectiveTopic: Tags

Use SemVer for GA (e.g., vX.Y.Z), suffix `-rc.N`/`-beta.N` for candidates, `-hotfix.N` for urgent patches, and build metadata for CI artifacts. Protect tags, sign GA tags, auto-generate notes via CI.

10. Which command lists commits between tags v1.1.0 (exclusive) and v1.2.0 (inclusive) on current branch?

Difficulty: MediumType: MCQTopic: Git Log

`A..B` shows commits reachable from B and not A; `...` is symmetric difference.

11. How do Git hosting releases relate to Git tags, and what extras do they provide?

Difficulty: EasyType: SubjectiveTopic: Releases

A release is metadata built around a tag: rich notes, attachments (artifacts), checksums, and visibility controls—useful for distributing binaries and changelogs.

12. Which command shows the most recent tag reachable from HEAD?

Difficulty: EasyType: MCQTopic: Tags

`git describe` finds the nearest tag; `--abbrev=0` prints only the tag name.

13. You want CI to cut a PATCH release on every merged hotfix PR. Which approach is most appropriate?

Difficulty: MediumType: MCQTopic: Tags

Automate SemVer bumps on protected branch and create annotated (optionally signed) tags with release notes.

More sets in Git & Version Control

Git & Version Control — Fundamentals(14+ Questions)
Git Branching & Collaboration — Core(14+ Questions)
Committing, Staging & History — Essentials(14+ Questions)
Remotes, Sync & Tags — Collaboration Deep Dive(14+ Questions)
Branching Strategies & Merge vs Rebase — History Hygiene(14+ Questions)
Rewriting History Safely — Reset, Revert, Reflog, Restore(14+ Questions)
Branching & Merging Strategies — Merge, Rebase, Fast-Forward(14+ Questions)
Stashing, Cleaning & Working Tree Maintenance(13+ Questions)
Branching Strategies, Pull Requests & Collaboration(13+ Questions)
Rebase, Cherry-pick & History Rewriting (Advanced)(12+ Questions)
Collaboration Workflows, Code Review & Best Practices(14+ Questions)

Explore related subjects

HTML CSS Javascript Typescript SQL & Databases React

Continue your preparation

For complete preparation, combine this set with full subject-wise practice for Git & Version Control. You can also explore other subjects and sets from the links below.

Quick navigation:Git & Version Control subject page•All subjects

Tags, Releases & Versioning (SemVer) in Git – Git & Version Control interview questions

Set overview

1. Which pair correctly deletes a remote tag v1.0.0 from origin after deleting it locally?

2. Why do teams create Git tags and when are annotated tags preferred over lightweight tags?

3. Which command creates an annotated tag named v1.2.0 with a message?

4. How do you push a single tag named v2.0.0 to origin?

5. In Semantic Versioning MAJOR.MINOR.PATCH, which increment signals backward-incompatible changes?

6. Which is a valid SemVer pre-release tag?

7. What should high-quality release notes include for a tagged release?

8. Which command creates a GPG-signed tag?

9. How would you design a tagging strategy for a service with weekly releases, hotfixes, and experimental builds?

10. Which command lists commits between tags v1.1.0 (exclusive) and v1.2.0 (inclusive) on current branch?

11. How do Git hosting releases relate to Git tags, and what extras do they provide?

12. Which command shows the most recent tag reachable from HEAD?

13. You want CI to cut a PATCH release on every merged hotfix PR. Which approach is most appropriate?

More sets in Git & Version Control

Explore related subjects

Continue your preparation

Master Interviews Anywhere, Anytime

Tags, Releases & Versioning (SemVer) in Git – Git & Version Control interview questions

Set overview

1. Which pair correctly deletes a remote tag v1.0.0 from origin after deleting it locally?

2. Why do teams create Git tags and when are annotated tags preferred over lightweight tags?

3. Which command creates an annotated tag named v1.2.0 with a message?

4. How do you push a single tag named v2.0.0 to origin?

5. In Semantic Versioning MAJOR.MINOR.PATCH, which increment signals backward-incompatible changes?

6. Which is a valid SemVer pre-release tag?

7. What should high-quality release notes include for a tagged release?

8. Which command creates a GPG-signed tag?

9. How would you design a tagging strategy for a service with weekly releases, hotfixes, and experimental builds?

10. Which command lists commits between tags v1.1.0 (exclusive) and v1.2.0 (inclusive) on current branch?

11. How do Git hosting releases relate to Git tags, and what extras do they provide?

12. Which command shows the most recent tag reachable from HEAD?

13. You want CI to cut a PATCH release on every merged hotfix PR. Which approach is most appropriate?

More sets in Git & Version Control

Explore related subjects

Continue your preparation

Master Interviews
Anywhere, Anytime