git-workflow

# Git Workflow ## Branching Strategy (GitHub Flow) ``` main ← production-ready at all times └── feature/add-user-export ← feature branches (short-lived) └── fix/login-rate-limit ← bug fix branches └── chore/upgrade-dependencies ← maintenance └── refactor/extract-auth-module ← refactoring ``` **Rules:** - `main` is protected — no direct pushes - Every change goes through a PR - PRs require at least 1 approval - CI must pass before merge - Branches are deleted after merge ## Branch Naming ```bash # Pattern: <type>/<short-description> feature/user-profile-page feature/export-orders-xlsx fix/refresh-token-cookie-samesite fix/n-plus-one-users-query chore/update-nestjs-10 refactor/extract-payment-service docs/add-api-endpoints-readme test/add-auth-integration-tests release/v2.1.0 # DO NOT use: johns-branch # ← no name, no context fix1 # ← too vague JIRA-1234 # ← jira IDs alone mean nothing wip # ← push to a real branch when ready ``` ## Commit Messages ``` <type>(<scope>): <short description> <optional body — wrap at 72 chars> <optional footer: BREAKING CHANGE or fixes #issue> ``` **Types:** ``` feat — new feature fix — bug fix refactor — code change that neither fixes a bug nor adds a feature perf — performance improvement test — adding or correcting tests docs — documentation only chore — build process, tooling, dependencies ci — CI/CD c...