Git Workflow & Standards

Standardizing how code is written, committed, and versioned is non-negotiable for maintaining velocity and history quality in distributed teams.

Commit Discipline

Tool / Standard	Status	Context
Conventional Commits	ADOPT	Strict structure (`feat:`, `fix:`, `chore:`) to enable automated changelogs and semantic versioning.
Pre-commit Hooks	ADOPT	Preventing bad code from entering the repo. Enforcing `ruff`, `mypy`, and secret detection locally.
Commitizen	TRIAL	CLI helper to ensure teams adhere to commit conventions without memorizing rules.
Semantic Versioning	ADOPT	Managing releases (SemVer) automatically based on commit history.

Strategy	Status	Context
Trunk Based Development	ADOPT	Short-lived feature branches merging directly to `main`. Ideal for CI/CD and rapid iteration.
GitFlow	HOLD	Too complex for modern continuous delivery. Reserved only for legacy software with strict release cycles.

Resource	Description
Conventional Commits	A specification for adding human and machine readable meaning to commit messages.
Semantic Versioning (SemVer)	The industry standard for software versioning rules and requirements.
Pre-commit Framework	A multi-language package manager for pre-commit hooks.