Commit messages

Write commit messages and pull request titles in the Conventional Commits format.

<type>[scope][!]: <description>

feat: add user profile page
fix(auth): resolve password reset issue
feat(api)!: require a project id when creating a todo

CI checks every pull request title. If it fails, edit the title and the check runs again. Commit messages aren’t checked, but use the same format.

Allowed types

Type	Use for
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only
`style`	Formatting, no meaning change
`refactor`	Neither a fix nor a feature
`perf`	A performance improvement
`test`	Adding or fixing tests
`chore`	Build process and tooling
`ci`	CI configuration and scripts
`build`	Build system or dependencies
`revert`	Reverting a commit
`release`	Release commits (automatic)
`deps`, `infra`, `security`, `env`, `i18n`, `ux`, `config`, `assets`, `meta`	Their obvious areas

The list comes from .github/workflows/pr-naming-conventions.yml.

Why it matters

release-please reads the merged history to bump versions, write changelogs, and open release pull requests.