Fix .gitea ISSUE_TEMPLATE casing conflict
All checks were successful
Deploy to Staging / Build Images (push) Successful in 22s
Deploy to Staging / Deploy to Staging (push) Successful in 36s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 5s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
All checks were successful
Deploy to Staging / Build Images (push) Successful in 22s
Deploy to Staging / Deploy to Staging (push) Successful in 36s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 5s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
This commit is contained in:
@@ -1,41 +1,70 @@
|
||||
name: "Chore"
|
||||
about: "Refactor, maintenance, dependency updates, cleanup"
|
||||
name: Chore / Maintenance
|
||||
about: Technical debt, refactoring, dependency updates, infrastructure
|
||||
title: "[Chore]: "
|
||||
labels:
|
||||
- "type/chore"
|
||||
- "status/backlog"
|
||||
- type/chore
|
||||
- status/backlog
|
||||
body:
|
||||
- type: textarea
|
||||
id: goal
|
||||
- type: markdown
|
||||
attributes:
|
||||
label: "Goal"
|
||||
description: "What needs to be done and why?"
|
||||
value: |
|
||||
## Chore / Maintenance Task
|
||||
Use this template for technical debt, refactoring, dependency updates, or infrastructure work.
|
||||
|
||||
- type: dropdown
|
||||
id: category
|
||||
attributes:
|
||||
label: Category
|
||||
description: What type of chore is this?
|
||||
options:
|
||||
- Refactoring
|
||||
- Dependency update
|
||||
- Performance optimization
|
||||
- Technical debt cleanup
|
||||
- Infrastructure / DevOps
|
||||
- Testing improvements
|
||||
- Documentation
|
||||
- Other
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: description
|
||||
attributes:
|
||||
label: Description
|
||||
description: What needs to be done and why?
|
||||
placeholder: "We need to refactor X because Y..."
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: scope
|
||||
attributes:
|
||||
label: "Scope"
|
||||
label: Scope / Files Affected
|
||||
description: What parts of the codebase will be touched?
|
||||
placeholder: |
|
||||
- Includes:
|
||||
- Excludes:
|
||||
- frontend/src/features/[name]/
|
||||
- backend/src/features/[name]/
|
||||
- docker-compose.yml
|
||||
validations:
|
||||
required: false
|
||||
|
||||
- type: textarea
|
||||
id: acceptance
|
||||
attributes:
|
||||
label: "Acceptance criteria"
|
||||
label: Definition of Done
|
||||
description: How do we know this is complete?
|
||||
placeholder: |
|
||||
- [ ] ...
|
||||
- [ ] ...
|
||||
- [ ] All tests pass
|
||||
- [ ] No new linting errors
|
||||
- [ ] Performance benchmark improved by X%
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: test_plan
|
||||
id: risks
|
||||
attributes:
|
||||
label: "Test plan"
|
||||
label: Risks / Breaking Changes
|
||||
description: Any potential issues or breaking changes to be aware of?
|
||||
validations:
|
||||
required: true
|
||||
required: false
|
||||
|
||||
Reference in New Issue
Block a user