Document team Git workflows and branching strategies
Create Git workflow documentation for:
**Team Size:** {{TEAM_SIZE}}
**Project Type:** {{PROJECT_TYPE}}
**Release Cycle:** {{RELEASE_CYCLE}}
**Current Workflow:** {{CURRENT_WORKFLOW}} (GitFlow, GitHub Flow, etc.)
**Specific Requirements:**
{{REQUIREMENTS}}
Generate comprehensive Git workflow documentation:
# Git Workflow Guide
## Overview
- Workflow summary
- When to use this workflow
- Key principles
## Branch Strategy
### Main Branches
| Branch | Purpose | Protection |
|--------|---------|------------|
| main | Production code | Protected |
| develop | Integration branch | Protected |
### Supporting Branches
#### Feature Branches
- Naming: `feature/description`
- Created from: develop
- Merged to: develop
#### Release Branches
- Naming: `release/v1.0.0`
- Created from: develop
- Merged to: main and develop
#### Hotfix Branches
- Naming: `hotfix/description`
- Created from: main
- Merged to: main and develop
## Workflow Procedures
### Starting New Work
```bash
# Create feature branch
git checkout develop
git pull origin develop
git checkout -b feature/my-feature
```
### Daily Workflow
```bash
# Keep branch updated
git fetch origin
git rebase origin/develop
```
### Completing Work
```bash
# Prepare for PR
git rebase -i origin/develop
git push origin feature/my-feature
```
## Commit Guidelines
### Commit Message Format
```
type(scope): subject
body
footer
```
### Types
- feat, fix, docs, style, refactor, test, chore
## Pull Request Process
1. Create PR
2. Request reviews
3. Address feedback
4. Merge
## Release Process
Step-by-step release procedure
## Hotfix Process
Emergency fix procedure
## Best Practices
- Dos and don'ts
- Common mistakesOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{TEAM_SIZE][{PROJECT_TYPE][{RELEASE_CYCLE][{CURRENT_WORKFLOW][{REQUIREMENTS]