34918d9921
* chore: add PR template, issue templates, and triage action Adds a complete contribution quality layer to reduce maintainer triage burden: - .github/pull_request_template.md — structured PR description with checklist enforcing target branch, one-concern rule, CI green, no print(), schema regeneration, and ADR/CONTEXT.md update requirements - .github/ISSUE_TEMPLATE/bug_report.yml — required-field YAML form; GitHub blocks submission until reproduction steps and environment are filled in - .github/ISSUE_TEMPLATE/feature_request.yml — required problem/proposal fields with duplicate-check prompt - .github/ISSUE_TEMPLATE/config.yml — disables blank issues; funnels questions to Discussions - .github/workflows/triage.yml — auto-closes issues and PRs from accounts younger than 7 days, and closes anything with an empty or unfilled body Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore: simplify to templates only — drop triage workflow - PR template: target main (not dev), strip TS/pnpm/ADR checklist items that aren't enforced in the current codebase yet - Remove .github/workflows/triage.yml — account-age and auto-close policy needs explicit maintainer sign-off before automation Issue templates and config.yml are unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore: drop CI-green item — no active CI workflow yet Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore: upgrade templates with feedback from #1222 and #1211 thread Bug report: - Add install method dropdown (Docker / pip / Windows / macOS) - Split into separate Expected Behaviour and Actual Behaviour fields - Add Model / Backend field for LLM-related bugs - Add prerequisites checkboxes: duplicate search, security vuln redirect, running latest main - Add Additional Information free-text field Feature request: - Add prerequisites checkboxes (searched issues, searched discussions, concrete proposal) - Add area dropdown (Chat/Email/Calendar/Cookbook/etc.) for triage - Rename and tighten Problem and Solution fields - Add Prior Art / Related Issues field - Add Alternatives Considered field config.yml: - Replace two generic links with three specific ones: Q&A discussions, Ideas discussions, and GitHub Security Advisories for vulnerabilities PR template: - Rename Summary section with clearer placeholder text - Add Linked Issue section (Fixes #NNN) - Add How to Test section with numbered placeholder steps - Add Screenshots section for UI changes - Add duplicate-search checklist item - Remove No print() item (style note, not a structural requirement) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
91 lines
3.1 KiB
YAML
91 lines
3.1 KiB
YAML
name: Feature Request
|
|
description: Propose a new feature or a concrete improvement to Odysseus.
|
|
labels: ["enhancement"]
|
|
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
**Before submitting:** search [open issues](https://github.com/pewdiepie-archdaemon/odysseus/issues)
|
|
and [discussions](https://github.com/pewdiepie-archdaemon/odysseus/discussions) first.
|
|
Feature requests that duplicate [ROADMAP.md](https://github.com/pewdiepie-archdaemon/odysseus/blob/main/ROADMAP.md)
|
|
or an existing open issue will be closed as duplicates.
|
|
|
|
If your idea needs community input before it becomes a concrete proposal,
|
|
start a [discussion](https://github.com/pewdiepie-archdaemon/odysseus/discussions/categories/ideas) instead.
|
|
|
|
- type: checkboxes
|
|
id: prerequisites
|
|
attributes:
|
|
label: Prerequisites
|
|
options:
|
|
- label: I searched [open issues](https://github.com/pewdiepie-archdaemon/odysseus/issues?q=is%3Aissue+is%3Aopen) and this has not already been proposed.
|
|
required: true
|
|
- label: I searched [discussions](https://github.com/pewdiepie-archdaemon/odysseus/discussions) and this is not already being debated there.
|
|
required: true
|
|
- label: This is a concrete, actionable proposal — not a vague "it would be nice if..." request.
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: area
|
|
attributes:
|
|
label: Area
|
|
description: Which part of the application does this affect?
|
|
options:
|
|
- Chat / Agent
|
|
- Email
|
|
- Calendar
|
|
- Documents / RAG
|
|
- Memory
|
|
- Cookbook / Local Models / GPU
|
|
- Search
|
|
- Notes / Editor
|
|
- Auth / Security
|
|
- Docker / Deployment
|
|
- UI / Frontend
|
|
- API / Backend
|
|
- MCP
|
|
- Testing / CI
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem or Motivation
|
|
description: What problem does this solve, or what use case does it enable? Be specific — "it would be better" is not enough.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Proposed Solution
|
|
description: Describe the behaviour or change you want to see. Include API shape, UI sketch, or code snippets if that helps make it concrete.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives Considered
|
|
description: What other approaches did you consider and why did you rule them out? If there is an existing workaround, describe it.
|
|
|
|
- type: textarea
|
|
id: prior-art
|
|
attributes:
|
|
label: Prior Art / Related Issues
|
|
description: Link any related issues, discussions, or external references that informed this proposal.
|
|
|
|
- type: dropdown
|
|
id: willing_to_implement
|
|
attributes:
|
|
label: Are you willing to implement this?
|
|
options:
|
|
- "Yes — I can open a PR"
|
|
- "Partially — I can help but need guidance"
|
|
- "No — I am only filing the request"
|
|
validations:
|
|
required: true
|