docs(workflow): formalize gitflow process and templates
This commit is contained in:
30
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
30
.github/ISSUE_TEMPLATE/feature_request.md
vendored
Normal file
@ -0,0 +1,30 @@
|
||||
---
|
||||
name: Feature request
|
||||
about: Propose a new capability aligned with product milestones
|
||||
title: "[Feature] "
|
||||
labels: enhancement
|
||||
assignees: ""
|
||||
---
|
||||
|
||||
## Problem
|
||||
|
||||
What user or business problem are we solving?
|
||||
|
||||
## Proposed Solution
|
||||
|
||||
Describe the minimum viable implementation.
|
||||
|
||||
## Scope
|
||||
|
||||
- In scope:
|
||||
- Out of scope:
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ]
|
||||
- [ ]
|
||||
|
||||
## GitFlow Plan
|
||||
|
||||
- Branch suggestion: `feature/<scope>-<short-description>`
|
||||
- Target milestone:
|
||||
Reference in New Issue
Block a user