DevOps Beginner
Conventional Commits¶
Conventional CommitsGitChangelog 3 min read
Standardizovane commit zpravy. Automaticky changelog a verzovani.
Format¶
feat(auth): add OAuth2 login
fix(api): handle null response
docs(readme): update installation
chore(deps): upgrade express to v5
BREAKING CHANGE: remove /api/v1
Automation¶
- commitlint - validace
- semantic-release - automaticky release
How to Implement¶
Conventional Commits define a structured format for commit messages: type(scope): description. The type determines the nature of the change — feat for new features, fix for bug fixes, docs for documentation, refactor for refactoring without behavior changes, test for tests, and chore for maintenance.
Combining with semantic-release automates the entire release process: based on commit messages since the last release, it automatically determines the next version (MAJOR/MINOR/PATCH), generates a changelog, creates a git tag, and publishes the package. Commitlint with a Husky git hook ensures developers follow the convention at commit time. This approach eliminates manual version decisions and ensures a consistent changelog for the entire team.
Shrnuti¶
Citelna historie + automatizovany changelog od prvniho dne.
Need Help with Implementation?¶
Our team has experience designing and implementing modern architectures. We’re happy to help.