Skip to main content
Git tags serve as fixed points—or landmarks—in your commit history, helping you mark version releases and other significant milestones. By leveraging tags, you can easily reference builds, rollback to stable states, and integrate seamlessly with CI/CD pipelines in Azure Repos or any Git-based workflow.
The image explains the role of Git tags, showing them as landmarks for important commits, typically used for version releases or highlighting significant changes. It includes a visual with a Git logo and version numbers V01 to V04.

Why use Git tags?

  • Create immutable release points for reproducibility
  • Simplify collaboration by referencing a specific state of the code
  • Automate deployments by targeting a tag in your pipeline

Types of Git tags

Annotated tags include metadata—such as the tagger’s name, date, and a descriptive message—making them ideal for public releases.

Creating tags

Listing all tags

Pushing tags to remote

Avoid force-pushing or rewriting existing tags, as this can lead to inconsistencies in collaborators’ repositories.

Checking out a tag

To view or revert to a tagged commit:
This puts your working directory in “detached HEAD” state. To make changes, create a new branch:

Sorting tags by semantic version

This ensures v1.10 appears after v1.2.

Integrating Git tags with Azure Repos

Tags pushed to Azure Repos can trigger build and release pipelines. For step-by-step guidance, see Git version control in Azure Repos.

Watch Video