格式化与代码
提交消息生成器
Conventional commits, scoped and footer-aware.
Runs in your browser
Commit message
feat: <subject>
编辑注
Understanding · The future-self bug-hunting memo, in 50 characters.
本深度章节目前仅有英文版本。上方的转换工具支持您的语言;长篇说明文章尚未翻译。
常见问题
Quick answers.
›What is the Conventional Commits specification?
It is a lightweight convention for commit messages that provides a set of rules for creating an explicit commit history. It follows the pattern `type(scope): description` to communicate intent.
›When should I use a breaking change footer?
Use a breaking change footer whenever the commit introduces a change that is not backwards compatible. This usually triggers a major version bump in semantic versioning.
›Are my commit messages stored on your server?
No. The generator runs entirely within your browser session. Your code snippets, scopes, and descriptions never leave your local device.
›What do the different commit types mean?
`feat` is for new features, `fix` for bug fixes, `docs` for documentation, and `refactor` for code changes that neither fix a bug nor add a feature.
大家也在搜索
相关工具