chore: add gitea templates
This commit is contained in:
102
.gitea/issue_template/bug-report.yaml
Normal file
102
.gitea/issue_template/bug-report.yaml
Normal file
@@ -0,0 +1,102 @@
|
||||
name: Bug Report
|
||||
about: Something is broken or behaving unexpectedly
|
||||
title: "[Bug] "
|
||||
labels:
|
||||
- bug
|
||||
body:
|
||||
- type: dropdown
|
||||
id: area
|
||||
attributes:
|
||||
label: Affected Area
|
||||
description: Which part of the application is affected?
|
||||
options:
|
||||
- Game Picker (selection, filters, weighting)
|
||||
- Game Manager (CRUD, import/export, packs)
|
||||
- Session Management (create, close, archive, notes)
|
||||
- History / Session Detail (display, pagination, filters)
|
||||
- Room Code / Player Count (ecast, monitoring)
|
||||
- Chat Log Import / Voting
|
||||
- Webhooks
|
||||
- Authentication / Admin
|
||||
- WebSocket / Real-time / Presence
|
||||
- PWA (install, offline, service worker)
|
||||
- UI / Styling / Responsiveness
|
||||
- API (backend endpoint)
|
||||
- Database / Migrations
|
||||
- Docker / Deployment
|
||||
- Other
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: dropdown
|
||||
id: deploy-method
|
||||
attributes:
|
||||
label: Deployment Method
|
||||
options:
|
||||
- Docker (docker-compose)
|
||||
- Local development (npm run dev)
|
||||
- Other
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: description
|
||||
attributes:
|
||||
label: Description
|
||||
description: Concise summary of what's wrong.
|
||||
placeholder: "When I do X, Y happens instead of Z."
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: steps
|
||||
attributes:
|
||||
label: Steps to Reproduce
|
||||
description: Minimal sequence to trigger the bug.
|
||||
placeholder: |
|
||||
1. Login as admin
|
||||
2. Navigate to Picker page
|
||||
3. Set player count filter to 3
|
||||
4. Click "Roll the Dice"
|
||||
5. Observe error
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: expected
|
||||
attributes:
|
||||
label: Expected Behavior
|
||||
placeholder: A game matching the filters should be selected.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: actual
|
||||
attributes:
|
||||
label: Actual Behavior
|
||||
placeholder: The page shows a spinner indefinitely and the console logs a 500 error.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: logs
|
||||
attributes:
|
||||
label: Relevant Logs / Errors
|
||||
description: Paste browser console errors, backend logs (`docker-compose logs backend`), or network responses. Wrap sensitive data.
|
||||
render: shell
|
||||
|
||||
- type: textarea
|
||||
id: environment
|
||||
attributes:
|
||||
label: Environment
|
||||
description: Browser, OS, Node version, Docker version — whatever is relevant.
|
||||
placeholder: |
|
||||
Browser: Firefox 128
|
||||
OS: macOS 15.3
|
||||
Docker: 27.x / Compose v2.x
|
||||
|
||||
- type: textarea
|
||||
id: context
|
||||
attributes:
|
||||
label: Additional Context
|
||||
description: Screenshots, related issues, workarounds tried, etc.
|
||||
1
.gitea/issue_template/config.yaml
Normal file
1
.gitea/issue_template/config.yaml
Normal file
@@ -0,0 +1 @@
|
||||
blank_issues_enabled: true
|
||||
87
.gitea/issue_template/feature-request.yaml
Normal file
87
.gitea/issue_template/feature-request.yaml
Normal file
@@ -0,0 +1,87 @@
|
||||
name: Feature Request
|
||||
about: Suggest a new feature or improvement to an existing one
|
||||
title: "[Feature] "
|
||||
labels:
|
||||
- enhancement
|
||||
body:
|
||||
- type: dropdown
|
||||
id: type
|
||||
attributes:
|
||||
label: Request Type
|
||||
options:
|
||||
- New feature
|
||||
- Enhancement to existing feature
|
||||
- UX / UI improvement
|
||||
- API addition or change
|
||||
- Developer experience / tooling
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: dropdown
|
||||
id: area
|
||||
attributes:
|
||||
label: Affected Area
|
||||
description: Which part of the application does this relate to?
|
||||
multiple: true
|
||||
options:
|
||||
- Game Picker
|
||||
- Game Manager
|
||||
- Session Management
|
||||
- History / Session Detail
|
||||
- Room Code / Player Count
|
||||
- Chat Log Import / Voting
|
||||
- Webhooks
|
||||
- Authentication / Admin
|
||||
- WebSocket / Real-time / Presence
|
||||
- PWA
|
||||
- UI / Styling
|
||||
- API (backend)
|
||||
- Database
|
||||
- Docker / Deployment
|
||||
- Documentation
|
||||
- Other
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: problem
|
||||
attributes:
|
||||
label: Problem / Motivation
|
||||
description: What problem does this solve, or what use case does it enable?
|
||||
placeholder: "During a stream, I need to X but currently have to Y which is slow because Z."
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: solution
|
||||
attributes:
|
||||
label: Proposed Solution
|
||||
description: Describe what you'd like to happen. Be specific about behavior, UI, or API shape if you have ideas.
|
||||
placeholder: |
|
||||
Add a "favorites" toggle on each game card in the Manager.
|
||||
Favorited games appear at the top of the picker pool.
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: alternatives
|
||||
attributes:
|
||||
label: Alternatives Considered
|
||||
description: Other approaches you thought about and why they're less ideal.
|
||||
|
||||
- type: dropdown
|
||||
id: priority
|
||||
attributes:
|
||||
label: How important is this to you?
|
||||
options:
|
||||
- Nice to have
|
||||
- Would improve my workflow noticeably
|
||||
- Blocking a use case I need
|
||||
validations:
|
||||
required: true
|
||||
|
||||
- type: textarea
|
||||
id: context
|
||||
attributes:
|
||||
label: Additional Context
|
||||
description: Mockups, screenshots, links to related issues, etc.
|
||||
Reference in New Issue
Block a user