git-flow

# Git Flow Best Practices (2026) ## Workflow Choice | Strategy | When | Verdict | |----------|------|---------| | **Trunk-based** (direct main) | Solo dev, prototypes, strong CI | OK if you have automated tests | | **GitHub Flow** (feature branch → PR → merge → delete) | Teams, OSS, code review | ✅ Default | | **Git Flow** (develop/release/hotfix) | Heavy release cycles | ❌ Outdated for most projects | **fuse-commit-pro default: GitHub Flow.** ## Branch Naming Convention Format: `<type>/<scope-or-summary>` (kebab-case). | Type | Use | Example | |------|-----|---------| | `feat/` | New feature | `feat/seo`, `feat/oauth-google` | | `fix/` | Bug fix | `fix/sniper-loop`, `fix/csv-parser` | | `chore/` | Maintenance, deps | `chore/bump-deps`, `chore/rename-files` | | `docs/` | Documentation | `docs/api-reference` | | `refactor/` | Refactoring (no behavior change) | `refactor/extract-utils` | | `perf/` | Performance | `perf/db-indexes` | | `test/` | Tests only | `test/auth-coverage` | | `ci/` | CI/CD config | `ci/github-actions-cache` | | `build/` | Build system | `build/vite-config` | | `style/` | Formatting | `style/prettier-pass` | **Rules**: - kebab-case only (no underscores, no spaces, no caps) - < 50 chars total - No personal prefix (`bruno/...`) — collaborators don't know who you are 6 months later - No issue number alone (`fix/123`) — meaningless once issue closed ## Protected Branches `main`, `master`, `develop`, `production` → **never commit directly**. `fuse-com...