Designs complete Git workflows with branching strategies, commit conventions, PR processes, and automation.
You are a DevOps engineer who designs efficient Git workflows. Design a Git workflow for this team. Team size: [NUMBER OF DEVELOPERS] Release frequency: [DAILY / WEEKLY / MONTHLY / CONTINUOUS] Current workflow: [DESCRIBE OR NONE] CI/CD maturity: [BASIC / INTERMEDIATE / ADVANCED] Environments: [LIST ENVIRONMENTS] Compliance needs: [SOC2 / HIPAA / NONE] Design: **Branching Strategy** ``` main (production) ├── develop (staging) │ ├── feature/TICKET-123-description │ ├── bugfix/TICKET-456-description │ └── experiment/description ├── release/v1.2.0 └── hotfix/critical-fix ``` **Branch Naming Conventions** - Pattern: `type/ticket-description` - Types: feature, bugfix, hotfix, release, experiment - Examples for each **Commit Message Format** ``` type(scope): subject body footer ``` - Types: feat, fix, docs, style, refactor, test, chore - Scope examples - Subject rules - Body guidelines - Footer conventions (breaking changes, issue refs) **Pull Request Process** 1. Branch creation 2. Development 3. PR template 4. Review requirements 5. CI checks 6. Merge strategy 7. Branch cleanup **PR Template** ```markdown ## Summary ## Type of Change ## Testing ## Checklist ``` **Merge Strategies** - Feature to develop: [squash / rebase / merge] - Develop to main: [strategy] - Hotfix: [strategy] - Rationale for each **Protection Rules** - Required reviewers - Status checks - Linear history - Signed commits **Release Process** - Versioning scheme (SemVer) - Changelog generation - Tag creation - Release notes **Conflict Resolution** - Guidelines - Escalation path **Automation** - PR labeling - Auto-assign reviewers - Stale branch cleanup - Release automation
You are a DevOps engineer who designs efficient Git workflows. Design a Git workflow for this team. Team size: [NUMBER OF DEVELOPERS] Release frequency: [DAILY / WEEKLY / MONTHLY / CONTINUOUS] Current workflow: [DESCRIBE OR NONE] CI/CD maturity: [BASIC / INTERMEDIATE / ADVANCED] Environments: [LIST ENVIRONMENTS] Compliance needs: [SOC2 / HIPAA / NONE] Design: **Branching Strategy** ``` main (production) ├── develop (staging) │ ├── feature/TICKET-123-description │ ├── bugfix/TICKET-456-description │ └── experiment/description ├── release/v1.2.0 └── hotfix/critical-fix ``` **Branch Naming Conventions** - Pattern: `type/ticket-description` - Types: feature, bugfix, hotfix, release, experiment - Examples for each **Commit Message Format** ``` type(scope): subject body footer ``` - Types: feat, fix, docs, style, refactor, test, chore - Scope examples - Subject rules - Body guidelines - Footer conventions (breaking changes, issue refs) **Pull Request Process** 1. Branch creation 2. Development 3. PR template 4. Review requirements 5. CI checks 6. Merge strategy 7. Branch cleanup **PR Template** ```markdown ## Summary ## Type of Change ## Testing ## Checklist ``` **Merge Strategies** - Feature to develop: [squash / rebase / merge] - Develop to main: [strategy] - Hotfix: [strategy] - Rationale for each **Protection Rules** - Required reviewers - Status checks - Linear history - Signed commits **Release Process** - Versioning scheme (SemVer) - Changelog generation - Tag creation - Release notes **Conflict Resolution** - Guidelines - Escalation path **Automation** - PR labeling - Auto-assign reviewers - Stale branch cleanup - Release automation
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Generates professional, semantic Git commit messages based on code changes or diffs.
Creates comprehensive PR templates and code review guidelines with checklists, comment conventions, and CODEOWNERS.
Creates complete CI/CD pipeline configurations with testing, security scanning, multi-environment deployment, and monitoring.
Creates comprehensive Architecture Decision Records with options analysis, decision matrices, and consequence documentation.