Add branching strategy documentation
- Create BRANCHING_STRATEGY.md with Git Flow workflow - Update README.md with branching overview - Document dev → staging → main flow - Include PR guidelines and best practices - Add emergency procedures and rollback instructions
This commit is contained in:
28
README.md
28
README.md
@@ -363,6 +363,34 @@ If a deployment fails but the name is marked as taken:
|
||||
|
||||
See `CLAUDE.md` for development guidelines and architecture documentation.
|
||||
|
||||
## Branching Strategy
|
||||
|
||||
This project uses a Git Flow branching model:
|
||||
|
||||
- **`main`** - Production branch (deployed to https://portal.ai.flexinit.nl)
|
||||
- **`staging`** - Pre-production testing environment
|
||||
- **`dev`** - Active development branch
|
||||
|
||||
### Workflow
|
||||
```
|
||||
feature/xyz → dev → staging → main
|
||||
```
|
||||
|
||||
### Quick Commands
|
||||
```bash
|
||||
# Start new feature
|
||||
git checkout dev
|
||||
git checkout -b feature/my-feature
|
||||
|
||||
# Deploy to staging (via PR)
|
||||
# Create PR: dev → staging
|
||||
|
||||
# Deploy to production (via PR)
|
||||
# Create PR: staging → main
|
||||
```
|
||||
|
||||
See `BRANCHING_STRATEGY.md` for complete workflow documentation.
|
||||
|
||||
## License
|
||||
|
||||
[Your License Here]
|
||||
|
||||
Reference in New Issue
Block a user