Replace the two flat markdown templates with validated YAML Issue Forms and a chooser config, so reports arrive with the diagnostic fields triage actually needs and "how do I…" traffic routes to chat instead. - `bug_report.yml` — dup-search + latest-version checkboxes; required what/repro/expected; OS / install-method / version / compute-device dropdowns (incl. ROCm + XPU); active-engine; logs (render: text) with the diagnostic- bundle + `--diagnose` tip up top. - `install_problem.yml` — NEW, for the "first-run that just works" core value: a failure-stage dropdown (launch / uv-bootstrap / model-download / engine- install / first-synth), required error + OS/install/version, and a network-conditions dropdown (proxy / restricted-region / offline) since restricted networks are a known bootstrap failure mode. - `feature_request.yml` — problem/solution/alternatives + an Area dropdown, with a local-first/cross-platform constraints note so proposals fit. - `config.yml` — `blank_issues_enabled: false`; contact links to Discord, Discussions, and the private security policy. Removes bug_report.md / feature_request.md (superseded). Forms validated (yaml parse); SECURITY.md backs the security link; CJK guard green.
12 lines
614 B
YAML
12 lines
614 B
YAML
blank_issues_enabled: false
|
|
contact_links:
|
|
- name: 💬 Discord — questions & quick help
|
|
url: https://discord.gg/bzQavDfVV9
|
|
about: Usage questions, setup help, and chat. Faster than an issue for "how do I…".
|
|
- name: 🗣️ GitHub Discussions
|
|
url: https://github.com/debpalash/OmniVoice-Studio/discussions
|
|
about: Ideas, show-and-tell, and open-ended Q&A that isn't a bug or a specific feature ask.
|
|
- name: 🔒 Security vulnerability
|
|
url: https://github.com/debpalash/OmniVoice-Studio/security/policy
|
|
about: Please report security issues privately — do NOT open a public issue.
|