フォーマッター＆コード
コミットメッセージジェネレーター
Conventional commits, scoped and footer-aware.
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.
他の人はこちらも検索しています
関連ツール