مولد رسائل الالتزام (Commit)

الأسئلة المتكررة

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.