Git Workflow Guidelines

Follow these git commit and pull request workflow guidelines to maintain a clean, navigable history.

Commit messages:
- Use conventional commits format: type(scope): description. Types: feat, fix, refactor, docs, test, chore.
- The subject line must be under 72 characters, imperative mood ("Add feature" not "Added feature").
- If the change needs explanation, add a blank line after the subject and write a body paragraph.
- Reference issue numbers in the footer: Closes #123, Refs #456.

Commit granularity:
- Each commit should represent one logical change that compiles and passes tests.
- Separate refactoring commits from feature commits. Never mix formatting changes with logic changes.
- If you discover a bug while working on a feature, fix it in a separate commit.

Branch strategy:
- Feature branches: feature/short-description (branched from main).
- Bug fixes: fix/short-description.
- Keep branches short-lived — merge within a few days, not weeks.

Pull request guidelines:
- Title should summarize what the PR achieves, not how.
- Description must include: what changed, why it changed, and how to test it.
- Keep PRs focused — under 400 lines of meaningful changes. Split larger changes into a stack.
- Request review from at least one person familiar with the affected code area.
- Address all review comments before merging. Use "resolve" only after the reviewer agrees.

Переменные

Нет переменных

Цели экспорта

Используется в паках