managing-gitlisted

# Managing Git ## Feature Development Workflow Copy this checklist and track progress: ``` Feature Development Progress: - [ ] Step 1: Create feature branch from main - [ ] Step 2: Make changes with atomic commits - [ ] Step 3: Rebase on latest main - [ ] Step 4: Push and create PR - [ ] Step 5: Address review feedback - [ ] Step 6: Merge after approval ``` ## Branching Strategies ### GitHub Flow (Recommended for most projects) ``` main ──●────●────●────●────●── (always deployable) \ / feature └──●──●──┘ ``` - `main` is always deployable - Feature branches from main - PR + review + merge - Deploy after merge ### Git Flow (For release-based projects) ``` main ──●─────────────●────── (releases only) \ / release └────●────┘ / develop ──●──●────●──●──●── \ / feature └──●┘ ``` ## Commit Conventions ### Conventional Commits Format ``` <type>(<scope>): <description> [optional body] [optional footer(s)] ``` ### Types | Type | Description | |------|-------------| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only | | `style` | Formatting, no logic change | | `refactor` | Code change that neither fixes bug nor adds feature | | `perf` | Performance improvement | | `test` | Adding/updating tests | | `chore` | Build process, dependencies | | `ci` | CI configuration | ### Examples ```bash feat(auth): add OAuth2 login support Implements Google and GitHub OAuth provide