Skip to content

Форматтеры и код

Генератор сообщений коммитов

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.

Люди также ищут

Связанные инструменты

More in this room.

Смотреть все в Форматтеры и код