Cómo usar: Changelog Generator
- Run the
git logcommand shown above in your repository and paste the output (hash + subject per line). - Enter the current version; the release version is suggested from the commits — or type your own.
- Choose Conventional or Keep a Changelog headings and add your repository URL to link commit hashes.
- Copy the Markdown to the top of your
CHANGELOG.mdor into a GitHub release.
Conventional Commits in 30 seconds
Each commit subject starts with a type, an optional scope and a description: feat(cart): add coupon field. A ! after the type/scope or a BREAKING CHANGE: note marks a breaking change.
| Type | Section | Version bump |
|---|---|---|
feat | Features / Added | Minor |
fix | Bug Fixes / Fixed | Patch |
perf | Performance | Patch |
feat!, BREAKING CHANGE | Breaking Changes | Major |
refactor, docs, style, test, build, ci, chore | Other / hidden | None |
revert | Reverts | Patch |
Keep a Changelog
Keep a Changelog groups entries for humans under Added, Changed, Deprecated, Removed, Fixed, Security, newest release first, with an Unreleased section at the top. Choose that style if your users read the changelog rather than developers.
From changelog to release
Check the suggested version with the Semantic Version Calculator, update version in your package.json, then tag and push the release — the Git Command Generator has the commands. A GitHub Actions workflow can build and publish on every tag.
También se busca como: conventional commits changelog, keep a changelog, release notes generator, changelog.md, git log changelog, semantic release notes, conventional commits.
Herramientas que combinan con: Changelog Generator
- Conventional Commit Builder — Write commit messages that follow the Conventional Commits spec without memorizing it.
- Generador de archivos README — Rellena unos cuantos campos y obtén un README.md — insignias, instalación, ejemplo de uso, tabla de configuración, variables de entorno, hoja de ruta y licencia — con vista previa en tiempo real y comprobación de que todo esté completo.
- YAML Validator — Paste a Docker Compose file, Kubernetes manifest, GitHub Actions workflow or any YAML to pinpoint errors, catch common pitfalls and get a cleanly formatted version.
- Kubernetes YAML Generator — Fill in your app’s name, image and port and get production-ready Kubernetes YAML: a Deployment with probes, resource limits and a hardened security context, plus the Service, Ingress with TLS, ConfigMap, Secret and HorizontalPodAutoscaler you tick — in one file ready for kubectl apply.
Preguntas frecuentes
What git log format should I paste?
git log --pretty=format:"%h %s". Plain subjects without hashes work too. Merge commits are skipped automatically.