Create a Git workflow and conventions guide for a team of [NUMBER] developers working on [PROJECT TYPE].
Provide:
1. **Branching Strategy**: Gitflow vs trunk-based (recommendation with reasoning)
2. **Branch Naming**: Convention with examples (feature/, bugfix/, hotfix/, release/)
3. **Commit Messages**: Format specification with examples
4. **Pull Request Template**: Description, checklist, reviewer guidelines
5. **Code Review Process**: Who reviews, turnaround time, approval requirements
6. **Merge Strategy**: Squash vs merge vs rebase (when to use each)
7. **Release Process**: Version tagging, changelog generation, deployment triggers
8. **CI/CD Integration**: Recommended checks (lint, test, build, security scan)
9. **.gitignore**: Comprehensive template for [LANGUAGE/FRAMEWORK]
10. **Common Scenarios**: How to handle merge conflicts, reverts, cherry-picks
Create a Git workflow and conventions guide for a team of [NUMBER] developers working on [PROJECT TYPE].
Provide:
1. **Branching Strategy**: Gitflow vs trunk-based (recommendation with reasoning)
2. **Branch Naming**: Convention with examples (feature/, bugfix/, hotfix/, release/)
3. **Commit Messages**: Format specification with examples
4. **Pull Request Template**: Description, checklist, reviewer guidelines
5. **Code Review Process**: Who reviews, turnaround time, approval requirements
6. **Merge Strategy**: Squash vs merge vs rebase (when to use each)
7. **Release Process**: Version tagging, changelog generation, deployment triggers
8. **CI/CD Integration**: Recommended checks (lint, test, build, security scan)
9. **.gitignore**: Comprehensive template for [LANGUAGE/FRAMEWORK]
10. **Common Scenarios**: How to handle merge conflicts, reverts, cherry-picks
How to use this prompt
Copy the prompt above and paste it into ChatGPT, Claude, Gemini, or any AI assistant. Replace the bracketed placeholders with your specific details.
Leave a Review
Tried this prompt? Let us know how it worked — your reviews help other users find the best prompts.