Replace Python CLI with Gitea issue tracker setup
Switch from a custom CLI ticketing tool to Gitea-native issue tracking. Add issue templates (bug, feature, task) and a curated initial backlog of 20 tickets covering project foundation, testing, security, docs, features, and community maintenance.
This commit is contained in:
36
.gitea/ISSUE_TEMPLATE/bug_report.md
Normal file
36
.gitea/ISSUE_TEMPLATE/bug_report.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
name: "🐛 Bug Report"
|
||||
about: "Report something that is broken or not working as expected."
|
||||
title: "[Bug] "
|
||||
labels: ["bug", "triage"]
|
||||
assignees: []
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
<!-- A clear, concise description of the bug. -->
|
||||
|
||||
## Steps to Reproduce
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
## Expected Behavior
|
||||
|
||||
<!-- What did you expect to happen? -->
|
||||
|
||||
## Actual Behavior
|
||||
|
||||
<!-- What actually happened? Include logs or screenshots if helpful. -->
|
||||
|
||||
## Environment
|
||||
|
||||
- **OS / Distro:**
|
||||
- **Browser / Runtime version:**
|
||||
- **Commit / Release:** <!-- e.g. main @ a1b2c3d -->
|
||||
|
||||
## Additional Context
|
||||
|
||||
<!-- Any other details that might help diagnose the issue. -->
|
||||
|
||||
10
.gitea/ISSUE_TEMPLATE/config.yml
Normal file
10
.gitea/ISSUE_TEMPLATE/config.yml
Normal file
@@ -0,0 +1,10 @@
|
||||
blank_issues_enabled: true
|
||||
|
||||
contact_links:
|
||||
- name: "❓ Ask a Question"
|
||||
url: https://gitea.arcline-project.local/
|
||||
about: "Use the discussions or chat instead."
|
||||
- name: "📖 Project Docs"
|
||||
url: https://docs.arcline-project.local/
|
||||
about: "Read the documentation before filing an issue."
|
||||
|
||||
28
.gitea/ISSUE_TEMPLATE/feature_request.md
Normal file
28
.gitea/ISSUE_TEMPLATE/feature_request.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
name: "✨ Feature Request"
|
||||
about: "Propose a new feature or enhancement."
|
||||
title: "[Feature] "
|
||||
labels: ["enhancement", "triage"]
|
||||
assignees: []
|
||||
---
|
||||
|
||||
## Problem Statement
|
||||
|
||||
<!-- What problem are you trying to solve? Why is this valuable? -->
|
||||
|
||||
## Proposed Solution
|
||||
|
||||
<!-- Describe the feature or enhancement you'd like to see. -->
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
<!-- Are there other ways to solve this? Why did you choose this approach? -->
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] <!-- Checkable criteria for when this is "done" -->
|
||||
|
||||
## Additional Context
|
||||
|
||||
<!-- Screenshots, references, or anything else that helps. -->
|
||||
|
||||
26
.gitea/ISSUE_TEMPLATE/task.md
Normal file
26
.gitea/ISSUE_TEMPLATE/task.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
name: "📋 Task / Epic"
|
||||
about: "Track a general task, investigation, or epic."
|
||||
title: "[Task] "
|
||||
labels: ["task"]
|
||||
assignees: []
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
<!-- One or two sentences describing the task. -->
|
||||
|
||||
## Subtasks
|
||||
|
||||
- [ ]
|
||||
- [ ]
|
||||
- [ ]
|
||||
|
||||
## Dependencies
|
||||
|
||||
<!-- Does this block or is it blocked by other issues? -->
|
||||
|
||||
## Notes
|
||||
|
||||
<!-- Links, design docs, or relevant context. -->
|
||||
|
||||
Reference in New Issue
Block a user