Dev
Git Tag Name Generator
Git tags that follow a consistent naming convention — a leading v, then the semantic version — are easier to sort, search, and process with tools like gh release and semantic-release. When you need format examples for documentation, test fixtures for a version-parsing script, or a demo release history, generating plausible tags is faster than inventing them by hand. This tool generates between 1 and 12 tag names. Each follows the v{major}.{minor}.{patch} format, with major from 0 to 3, minor from 0 to 11, and patch from 0 to 19. About 30% of the generated tags include a pre-release suffix — one of -alpha.1, -beta.1, -beta.2, or -rc.1 — mirroring the mix of stable and pre-release tags in a real project's history. The generator deduplicates the output. Use the tags as format examples in release documentation, feed them to version-parsing test cases, or populate a mock release list. For real releases, choose the version number based on what changed — major for breaking changes, minor for new features, patch for fixes — rather than using a randomly generated number.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many tag names you want.
- Click Generate to produce Git tags.
- Use them as format examples.
- Tag real releases with your real version.
Use Cases
- •Examples for release documentation
- •Testing version-tag parsing
- •Learning the Git tagging convention
- •Filling sample release data
- •Demoing a release workflow
Tips
- →Prefix tags with v by convention.
- →Use -rc, -beta for pre-releases.
- →Follow your real version sequence.
- →Keep tags consistent for tooling.
FAQ
how should I name a Git release tag
The common convention is a leading v followed by a semantic version — v1.4.0 — with optional pre-release suffixes like -beta.1 or -rc.1. This keeps tags readable and lets tooling sort and compare releases reliably.
what does -rc.1 mean in a tag
It marks a release candidate — a build that is potentially the final release, pending testing. Pre-release suffixes like alpha, beta, and rc signal that a version is not yet stable, and semver orders them before the final release.
should real tags use random numbers
No. Real release tags should follow your actual version sequence, bumping major, minor, or patch according to what changed. These generated tags are format examples for documentation and testing, not literal versions to use.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.