diff options
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r-- | .github/ISSUE_TEMPLATE | 26 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/1_dont_ignore.md | 16 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/2_bug_report_linux.md | 55 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/2_bug_report_macos.md | 57 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/2_bug_report_windows.md | 54 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/3_bug_report.md | 54 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/4_bug_report_build.md | 35 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/5_feature_request.md | 21 | ||||
-rw-r--r-- | .github/ISSUE_TEMPLATE/config.yml | 9 |
9 files changed, 301 insertions, 26 deletions
diff --git a/.github/ISSUE_TEMPLATE b/.github/ISSUE_TEMPLATE deleted file mode 100644 index 3497ea04f4..0000000000 --- a/.github/ISSUE_TEMPLATE +++ /dev/null @@ -1,26 +0,0 @@ -### mpv version and platform - -If you're not using git master or the latest release, update. -Releases are listed here: https://github.com/mpv-player/mpv/releases - -### Reproduction steps - -### Expected behavior - -### Actual behavior - -### Log file - -Make a log file made with -v or --log-file=output.txt, paste it to -https://0x0.st/ or a similar site, and replace this text with a link to it. - -Providing a log file is strongly encouraged. It is very helpful for reproducing -bugs or getting important technical context. Without a log it might not be -possible to analyze and fix certain bugs, and your bug report will be closed -or ignored. - -### Sample files - -Sample files needed to reproduce this issue can be uploaded to https://0x0.st/ -or similar sites. (Only needed if the issue cannot be reproduced without it.) -Do not use garbage like "cloud storage", especially not Google Drive.
\ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/1_dont_ignore.md b/.github/ISSUE_TEMPLATE/1_dont_ignore.md new file mode 100644 index 0000000000..578d5604fd --- /dev/null +++ b/.github/ISSUE_TEMPLATE/1_dont_ignore.md @@ -0,0 +1,16 @@ +--- +name: 'README: DO NOT IGNORE OR DELETE THE ISSUE TEMPLATE' +about: 'Chose and fill out one of the following templates!' +title: '' +labels: priority:ignored-issue-template +assignees: '' + +--- + +We ask you to not ignore the issue template. Fill it out as good and correct as +possible. Issues that don't adhere to our request will be closed for ignoring +the issue template. This is because analyzing a bug without a log file is harder +than necessary. Low quality bug reports are noise. + +Please go back and chose the proper issue template. Opening issues with this +template will be closed immediately. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md new file mode 100644 index 0000000000..e8e30d1931 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md @@ -0,0 +1,55 @@ +--- +name: 'Report a Linux Issue' +about: 'Create a report for a runtime related Linux Issue' +title: '' +labels: 'os:linux' +assignees: '' + +--- + +### Important Information + +Provide following Information: +- mpv version +- Linux Distribution and Version +- Source of the mpv binary +- If known which version of mpv introduced the problem +- Window Manager and version +- GPU model, driver and version +- Possible screenshot or video of visual glitches + +If you're not using git master or the latest release, update. +Releases are listed here: https://github.com/mpv-player/mpv/releases + +### Reproduction steps + +Try to reproduce your issue with --no-config first. If it isn't reproducible +with --no-config try to first find out which option or script causes your issue. + +If the issue is performance-related, try to reproduce it with --no-config +--profile=fast, which is designed to work on lower-end mobile devices. +Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut. + +Describe the reproduction steps as precise as possible. It's very likely that +the bug you experience wasn't reproduced by the developer because the workflow +differs from your own. + +### Expected behavior + +### Actual behavior + +### Log file + +Make a log file made with -v -v or --log-file=output.txt, attach it to +the issue, and replace this text with a link to it. + +Without the log file, this issue will be closed for ignoring the issue template. + +In the case of a crash, please provide a backtrace. + +### Sample files + +Sample files needed to reproduce this issue can be attached to the issue +(preferred), or be uploaded to https://0x0.st/ or similar sites. +(Only needed if the issue cannot be reproduced without it.) +Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md b/.github/ISSUE_TEMPLATE/2_bug_report_macos.md new file mode 100644 index 0000000000..470b4a0922 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_macos.md @@ -0,0 +1,57 @@ +--- +name: 'Report a macOS Issue' +about: 'Create a report for a runtime related macOS Issue' +title: '' +labels: 'os:mac' +assignees: '' + +--- + +### Important Information + +Provide following Information: +- mpv version +- macOS Version +- Source of the mpv binary or bundle +- If known which version of mpv introduced the problem +- Possible screenshot or video of visual glitches + +If you're not using git master or the latest release, update. +Releases are listed here: https://github.com/mpv-player/mpv/releases + +### Reproduction steps + +Try to reproduce your issue with --no-config first. If it isn't reproducible +with --no-config try to first find out which option or script causes your issue. + +If the issue is performance-related, try to reproduce it with --no-config +--profile=fast, which is designed to work on lower-end mobile devices. +Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut. + +Describe the reproduction steps as precise as possible. It's very likely that +the bug you experience wasn't reproduced by the developer because the workflow +differs from your own. + +### Expected behavior + +### Actual behavior + +### Log file + +Make a log file made with -v -v or --log-file=output.txt, attach it to +the issue, and replace this text with a link to it. + +If you use the Bundle, a default log is created for your last run at +~/Library/Logs/mpv.log. You can jump to that file via the +Help > Show log Fileā¦ menu. + +Without the log file, this issue will be closed for ignoring the issue template. + +In the case of a crash, please provide the macOS Crash Report (Backtrace). + +### Sample files + +Sample files needed to reproduce this issue can be attached to the issue +(preferred), or be uploaded to https://0x0.st/ or similar sites. +(Only needed if the issue cannot be reproduced without it.) +Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md b/.github/ISSUE_TEMPLATE/2_bug_report_windows.md new file mode 100644 index 0000000000..d936593615 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_windows.md @@ -0,0 +1,54 @@ +--- +name: 'Report a Windows Issue' +about: 'Create a report for a runtime related Windows Issue' +title: '' +labels: 'os:win' +assignees: '' + +--- + +### Important Information + +Provide following Information: +- mpv version +- Windows Version +- Source of the mpv binary +- If known which version of mpv introduced the problem +- GPU model, driver and version +- Possible screenshot or video of visual glitches + +If you're not using git master or the latest release, update. +Releases are listed here: https://github.com/mpv-player/mpv/releases + +### Reproduction steps + +Try to reproduce your issue with --no-config first. If it isn't reproducible +with --no-config try to first find out which option or script causes your issue. + +If the issue is performance-related, try to reproduce it with --no-config +--profile=fast, which is designed to work on lower-end mobile devices. +Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut. + +Describe the reproduction steps as precise as possible. It's very likely that +the bug you experience wasn't reproduced by the developer because the workflow +differs from your own. + +### Expected behavior + +### Actual behavior + +### Log file + +Make a log file made with -v -v or --log-file=output.txt, attach it to +the issue, and replace this text with a link to it. + +Without the log file, this issue will be closed for ignoring the issue template. + +In the case of a crash, please provide a backtrace. + +### Sample files + +Sample files needed to reproduce this issue can be attached to the issue +(preferred), or be uploaded to https://0x0.st/ or similar sites. +(Only needed if the issue cannot be reproduced without it.) +Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/3_bug_report.md b/.github/ISSUE_TEMPLATE/3_bug_report.md new file mode 100644 index 0000000000..e33a003cf0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/3_bug_report.md @@ -0,0 +1,54 @@ +--- +name: 'Report a different Issue' +about: 'Create a report for a runtime related Issue' +title: '' +labels: '' +assignees: '' + +--- + +### Important Information + +Provide following Information: +- mpv version +- Platform and Version +- Source of the mpv binary +- If known which version of mpv introduced the problem +- GPU model, driver and version +- Possible screenshot or video of visual glitches + +If you're not using git master or the latest release, update. +Releases are listed here: https://github.com/mpv-player/mpv/releases + +### Reproduction steps + +Try to reproduce your issue with --no-config first. If it isn't reproducible +with --no-config try to first find out which option or script causes your issue. + +If the issue is performance-related, try to reproduce it with --no-config +--profile=fast, which is designed to work on lower-end mobile devices. +Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut. + +Describe the reproduction steps as precise as possible. It's very likely that +the bug you experience wasn't reproduced by the developer because the workflow +differs from your own. + +### Expected behavior + +### Actual behavior + +### Log file + +Make a log file made with -v -v or --log-file=output.txt, attach it to +the issue, and replace this text with a link to it. + +Without the log file, this issue will be closed for ignoring the issue template. + +In the case of a crash, please provide a backtrace. + +### Sample files + +Sample files needed to reproduce this issue can be attached to the issue +(preferred), or be uploaded to https://0x0.st/ or similar sites. +(Only needed if the issue cannot be reproduced without it.) +Do not use garbage like "cloud storage", especially not Google Drive. diff --git a/.github/ISSUE_TEMPLATE/4_bug_report_build.md b/.github/ISSUE_TEMPLATE/4_bug_report_build.md new file mode 100644 index 0000000000..8370a300ae --- /dev/null +++ b/.github/ISSUE_TEMPLATE/4_bug_report_build.md @@ -0,0 +1,35 @@ +--- +name: 'Report a build Problem' +about: 'Create a report for a build related Issue' +title: '' +labels: 'core:meson' +assignees: '' + +--- + +### Important Information + +Provide following Information: +- mpv version +- Platform and Version +- meson version + +If you're not using git master or the latest release, update. +Releases are listed here: https://github.com/mpv-player/mpv/releases + +### Reproduction steps + +Describe the reproduction steps as precise as possible. It's very likely that +the bug you experience wasn't reproduced by the developer because the workflow +differs from your own. + +### Expected behavior + +### Actual behavior + +### Log file + +Attach meson-logs/meson-log.txt or meson setup build output to the issue, +and replace this text with a link to it. + +Without the log file, this issue will be closed for ignoring the issue template. diff --git a/.github/ISSUE_TEMPLATE/5_feature_request.md b/.github/ISSUE_TEMPLATE/5_feature_request.md new file mode 100644 index 0000000000..a28062253c --- /dev/null +++ b/.github/ISSUE_TEMPLATE/5_feature_request.md @@ -0,0 +1,21 @@ +--- +name: 'Request a new Feature' +about: 'Create a request for a new feature' +title: '' +labels: 'meta:feature-request' +assignees: '' + +--- + +Before requesting a new feature make sure it hasn't been requested yet. +https://github.com/mpv-player/mpv/labels/meta%3Afeature-request + +### Expected behavior of the wanted feature + +### Alternative behavior of the wanted feature + +### Log file + +Even if you think it's not necessary at first, it might help us later to find +possible issues. Make a log file made with -v -v or --log-file=output.txt, +attach it to the issue, and replace this text with a link to it. diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000000..536ac9cc32 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,9 @@ +blank_issues_enabled: false +contact_links: + - name: mpv IRC channel + url: https://mpv.io/community/ + about: Feel free to ask questions here irc://irc.libera.chat/mpv + - name: mpv IRC developer channel + url: https://mpv.io/community/ + about: Ask questions related to the development of mpv here + irc://irc.libera.chat/mpv-devel |