Files
4grayandClaude Opus 5.5 1b583ce648 chore(github): replace issue templates with issue forms
The Markdown bug and feature templates still asked "PWA or
Electron/Tauri application" with 0.16.0 as the example version, and
as free text they were mostly left unfilled: in the September backlog
triage only about a third of bug reports named the version or the
player, and 34 had to be sent back for a retest because they could
not be tied to a fix.

Replace them with GitHub issue forms that make the version, install
method, OS, source type and selected player required fields, ask
whether the problem is a regression, and point to Copy diagnostics.
Add a dedicated form for playback problems, the largest class of
reports, and a config that disables blank issues and links questions
to Discussions, the Docker guide and the website.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 11:03:28 +02:00

12 lines
588 B
YAML

blank_issues_enabled: false
contact_links:
- name: 💬 Questions and help
url: https://github.com/4gray/iptvnator/discussions
about: Ask how to set something up, or share ideas with other users.
- name: 🐳 Self-hosting with Docker
url: https://github.com/4gray/iptvnator/blob/master/docker/README.md
about: Setup, environment variables and reverse-proxy notes for the self-hosted web app.
- name: 🌐 Website and downloads
url: https://4gray.github.io/iptvnator/
about: Download links for every platform, FAQ and release announcements.