Generátor Git commit zpráv
Napište jasné, konvenční commit zprávy podle Conventional Commits nebo formátu vašeho týmu. Zahrnuje scope, typ a indikátory breaking changes.
Jak používat Generátor Git commit zpráv
- Describe the changes you made in plain language — what files changed, what behavior is different, and why you made the change.
- Select your team's commit convention (Conventional Commits is the most widely adopted).
- Choose the change type that best categorizes your change — 'feat' for new features, 'fix' for bug fixes, 'refactor' for restructuring.
- Optionally add a scope to narrow the context (e.g., 'auth' for authentication changes, 'ui' for frontend updates).
Případy použití
Write consistent commit messages across a team of developers
Generate commit messages that work with automated changelog generators
Create descriptive commits for open-source contributions and pull requests
Document complex refactoring changes with clear before/after context
Tipy pro nejlepší výsledky
- Include the 'why' in your description, not just the 'what' — this helps generate commit bodies that provide valuable context for future developers.
- Use specific scopes for monorepos: 'api', 'web', 'shared', 'infra' — this makes git log filtering much more useful.
- For breaking changes, mention what the old behavior was and what it is now — the generator will format a proper BREAKING CHANGE footer.
- The Conventional Commits format enables automatic version bumping and changelog generation with tools like semantic-release and standard-version.
Často kladené otázky
What is Conventional Commits?
Conventional Commits is a specification for commit messages that provides a structured format: type(scope): description. It enables automatic changelog generation, semantic version bumping, and makes git history searchable. It is the most widely adopted commit convention in the industry.
Should I use the subject-only or detailed version?
Use subject-only for small, self-explanatory changes (typo fixes, dependency updates). Use the detailed version with a body for feature additions, bug fixes, refactors, or any change where future developers will benefit from understanding the reasoning.
What scope should I use?
Scopes represent the section of the codebase affected: 'auth' for authentication, 'api' for REST endpoints, 'ui' for frontend components, 'db' for database changes, 'ci' for pipeline changes. Use scopes consistently across your team — leave blank for cross-cutting changes.
How does this help with changelogs?
Conventional Commits format is machine-readable. Tools like semantic-release, standard-version, and release-please can parse your commits to automatically generate categorized changelogs (Features, Bug Fixes, Breaking Changes) and determine version numbers.
What is the 72-character rule?
Git and many tools display the first line of a commit message as a summary. Keeping subject lines under 72 characters ensures they display fully in git log, GitHub, and IDE interfaces without being truncated. The body should also wrap at 72 characters for terminal readability.
Váš text neukládáme. Zpracování probíhá v reálném čase a váš vstup je okamžitě po vygenerování výsledku smazán.
Odemkněte neomezený přístup
Zdarma: 10 použití denně | Pro: Neomezeně