Branches must follow the pattern <type>/<description>, where <description> uses kebab-case.
Accepted prefixes:
| Prefix | When to use |
|---|---|
feature/ or feat/ |
New feature or enhancement |
fix/ |
Bug fix |
refactor/ |
Code refactoring without behaviour change |
chore/ |
Maintenance, dependency updates, tooling |
docs/ |
Documentation only |
style/ |
Code style / formatting changes |
build/ |
Build system or CI changes |
release/ |
Release preparation |
Both
feature/andfeat/are accepted as equivalent aliases for feature branches.
Examples:
feature/add-login-form
feat/add-login-form
fix/null-pointer-crash
release/1.2.0
Follow Conventional Commits:
<type>[(scope)]: <lowercase description>
Accepted types: feat, fix, chore, refactor, test, docs, style, ci, perf, build,
revert.
- Description must start with a lowercase letter.
- No Cyrillic characters anywhere in commit messages.
Examples:
feat: add biometric login
fix(api): handle null response from signaling
chore: upgrade flutter to 3.32.4
Hooks are managed with Lefthook.
brew install lefthook
lefthook installHooks run automatically:
- pre-commit —
dart formaton staged Dart files (generated files excluded) - commit-msg — validates commit message format
- pre-push — validates branch name, runs
flutter analyzeandflutter test
For installation details, manual execution, and troubleshooting see docs/development.md.