Chapter 3: Branching, Merge and GitHub PRs
3.7 Tags and releases (light)
In short: A tag is a name pointing at a specific commit — useful for versions people can talk about (v0.1.0).
A tag is a name pointing at a specific commit — useful for versions people can talk about (v0.1.0).
git tag v0.1.0
git tag -a v0.1.0 -m "First badge API hello release"
git push origin v0.1.0
Why. Pipelines and rollback notes say "deploy tag v0.1.0" more clearly than a long hash.
On GitHub, Releases can attach notes to a tag. For this chapter, creating one annotated tag is enough. Deep release automation comes with CI later.
| Use | Prefer |
|---|---|
| Daily work | Feature branches + PRs |
| "What is in production?" | Tag or image tag that matches the commit |
| Long-lived divergence | Avoid — merge often instead |
Ravindra Bagale's Tip
Khup students latest tag var depend kartat. Prod madhe immutable version (v0.1.0 or commit SHA) safer. latest lab sathi theva. Lakshat theva!