diff --git a/.github/ISSUE_TEMPLATE/1_dont_ignore.md b/.github/ISSUE_TEMPLATE/1_dont_ignore.md deleted file mode 100644 index 578d5604fd..0000000000 --- a/.github/ISSUE_TEMPLATE/1_dont_ignore.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -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/1_dont_ignore.yml b/.github/ISSUE_TEMPLATE/1_dont_ignore.yml new file mode 100644 index 0000000000..0441396909 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/1_dont_ignore.yml @@ -0,0 +1,21 @@ +name: "README: DO NOT IGNORE OR DELETE THE ISSUE TEMPLATE" +description: "Chose and fill out one of the following templates!" +labels: ["priority:ignored-issue-template"] +body: +- type: markdown + attributes: + value: > + 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. +- type: checkboxes + attributes: + label: "I ignored the issue template" + options: + - label: "Ignored the issue template" + required: true diff --git a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md b/.github/ISSUE_TEMPLATE/2_bug_report_linux.md deleted file mode 100644 index e8e30d1931..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_linux.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -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_linux.yml b/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml new file mode 100644 index 0000000000..25534a6bc4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_linux.yml @@ -0,0 +1,77 @@ +name: "Report a Linux Issue" +description: "Create a report for a runtime related Linux Issue" +labels: ["os:linux"] +body: +- type: textarea + attributes: + label: "Important Information" + description: > + - 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). + value: |- + - mpv version: + - Linux version: + - Source: + - Introduced in version: + - Window Manager and version: + - GPU model, driver and version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to 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. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to + the issue. + + In the case of a crash, please provide a backtrace. + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + 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 deleted file mode 100644 index 470b4a0922..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_macos.md +++ /dev/null @@ -1,57 +0,0 @@ ---- -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_macos.yml b/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml new file mode 100644 index 0000000000..b8457d49e5 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_macos.yml @@ -0,0 +1,75 @@ +name: "Report a macOS Issue" +description: "Create a report for a runtime related macOS Issue" +labels: ["os:mac"] +body: +- type: textarea + attributes: + label: "Important Information" + description: > + - 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). + value: |- + - mpv version: + - macOS version: + - Source: + - Introduced in version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to 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. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to + the issue. 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. + + In the case of a crash, please provide the macOS Crash Report (Backtrace). + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + 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 deleted file mode 100644 index d936593615..0000000000 --- a/.github/ISSUE_TEMPLATE/2_bug_report_windows.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -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/2_bug_report_windows.yml b/.github/ISSUE_TEMPLATE/2_bug_report_windows.yml new file mode 100644 index 0000000000..e19d82a5dc --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2_bug_report_windows.yml @@ -0,0 +1,75 @@ +name: "Report a Windows Issue" +description: "Create a report for a runtime related Windows Issue" +labels: ["os:win"] +body: +- type: textarea + attributes: + label: "Important Information" + description: > + - 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). + value: |- + - mpv version: + - Windows version: + - Source: + - Introduced in version: + - GPU model, driver and version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to 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. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to + the issue. + + In the case of a crash, please provide a backtrace. + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + 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 deleted file mode 100644 index e33a003cf0..0000000000 --- a/.github/ISSUE_TEMPLATE/3_bug_report.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -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/3_bug_report.yml b/.github/ISSUE_TEMPLATE/3_bug_report.yml new file mode 100644 index 0000000000..d2aa5e52b4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/3_bug_report.yml @@ -0,0 +1,75 @@ +name: "Report a different Issue" +description: "Create a report for a runtime related Issue" +labels: [] +body: +- type: textarea + attributes: + label: "Important Information" + description: > + - 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). + value: |- + - mpv version: + - Platform version: + - Source: + - Introduced in version: + - GPU model, driver and version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + Try to reproduce your issue with `--no-config` first. If it isn't reproducible + with `--no-config` try to 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. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to + the issue. + + In the case of a crash, please provide a backtrace. + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true +- type: textarea + attributes: + label: "Sample Files" + placeholder: "Drag and drop sample files here" + description: > + 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 deleted file mode 100644 index 8370a300ae..0000000000 --- a/.github/ISSUE_TEMPLATE/4_bug_report_build.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -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/4_bug_report_build.yml b/.github/ISSUE_TEMPLATE/4_bug_report_build.yml new file mode 100644 index 0000000000..a64feabaa9 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/4_bug_report_build.yml @@ -0,0 +1,51 @@ +name: "Report a build Problem" +description: "Create a report for a build related Issue" +labels: ["core:meson"] +body: +- type: textarea + attributes: + label: "Important Information" + description: > + - 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). + value: |- + - mpv version: + - Platform version: + - Meson version: + validations: + required: true +- type: textarea + attributes: + label: "Reproduction Steps" + description: > + 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. + validations: + required: true +- type: textarea + attributes: + label: "Expected Behavior" + placeholder: "What were you expecting?" + validations: + required: true +- type: textarea + attributes: + label: "Actual Behavior" + placeholder: "What happened instead?" + validations: + required: true +- type: textarea + attributes: + label: "Log File" + placeholder: "Drag and drop log file here (Don't paste content directly)" + description: > + Attach meson-logs/meson-log.txt or meson setup build output to the issue. + + Without the log file, this issue will be closed for ignoring the issue template. + validations: + required: true diff --git a/.github/ISSUE_TEMPLATE/5_feature_request.md b/.github/ISSUE_TEMPLATE/5_feature_request.md deleted file mode 100644 index a28062253c..0000000000 --- a/.github/ISSUE_TEMPLATE/5_feature_request.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -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/5_feature_request.yml b/.github/ISSUE_TEMPLATE/5_feature_request.yml new file mode 100644 index 0000000000..b9bfe1f57e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/5_feature_request.yml @@ -0,0 +1,22 @@ +name: "Request a new Feature" +description: "Create a request for a new feature" +labels: ["meta:feature-request"] +body: +- type: textarea + attributes: + label: "Expected behavior of the wanted feature" + description: > + Before requesting a new feature make sure it hasn't been + [requested yet](https://github.com/mpv-player/mpv/labels/meta%3Afeature-request). + validations: + required: true +- type: textarea + attributes: + label: "Alternative behavior of the wanted feature" +- type: textarea + attributes: + label: "Log File" + description: > + 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` and + attach it to the issue.