How would you use Git tags and release branches in a production release workflow?

Git tags vs release branches

Explains how tags and release branches support traceability, hotfixes, and production versioning.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A tag marks a specific commit, often the exact commit deployed as a version. A release branch is a branch used to stabilize or maintain a release line. I would use tags to identify what is running in production. I would use release branches when we need to prepare a release separately from ongoing main development or maintain hotfixes for a released version.

Full answer below

Practice focus

Release traceability, hotfix flow, version marking, production history, and branch lifecycle.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Tags and release branches solve different release-management problems. Choosing deliberately keeps production versions traceable while still allowing controlled maintenance.
A tag marks a specific commit, often the exact commit deployed as a version. A release branch is a branch used to stabilize or maintain a release line. I would use tags to identify what is running in production. I would use release branches when we need to prepare a release separately from ongoing main development or maintain hotfixes for a released version.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
When version 1.8.0 is deployed, I create a protected or signed tag on the exact commit so logs, artifacts, incidents, and rollback decisions share one immutable identity. A release branch is justified when 1.8 must stabilize or receive supported fixes while main continues toward . Every fix has a defined path back to main, usually through a reviewed cherry-pick or merge, so the release line does not become a separate forgotten product. Teams shipping continuously from one supported line may need only protected main, tags, and short-lived hotfix branches.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using tags as moving labels.
Keeping release branches forever with no owner.
Forgetting to merge hotfixes back to main.
Not tagging deployed versions.

How would you use Git tags and release branches in a production release workflow?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Suggest an improvement