History

github/issue_template: rework issue templates with github forms

der richter committed 2 years ago

Commit d4d5fa01 parent 7fd305d14 files · +396 −292Browse files

Unified · Split

14 files
  1. .github/ISSUE_TEMPLATE/1_dont_ignore.md +0 −16
  2. .github/ISSUE_TEMPLATE/1_dont_ignore.yml +21 −0
  3. .github/ISSUE_TEMPLATE/2_bug_report_linux.md +0 −55
  4. .github/ISSUE_TEMPLATE/2_bug_report_linux.yml +77 −0
  5. .github/ISSUE_TEMPLATE/2_bug_report_macos.md +0 −57
  6. .github/ISSUE_TEMPLATE/2_bug_report_macos.yml +75 −0
  7. .github/ISSUE_TEMPLATE/2_bug_report_windows.md +0 −54
  8. .github/ISSUE_TEMPLATE/2_bug_report_windows.yml +75 −0
  9. .github/ISSUE_TEMPLATE/3_bug_report.md +0 −54
  10. .github/ISSUE_TEMPLATE/3_bug_report.yml +75 −0
  11. .github/ISSUE_TEMPLATE/4_bug_report_build.md +0 −35
  12. .github/ISSUE_TEMPLATE/4_bug_report_build.yml +51 −0
  13. .github/ISSUE_TEMPLATE/5_feature_request.md +0 −21
  14. .github/ISSUE_TEMPLATE/5_feature_request.yml +22 −0
.github/ISSUE_TEMPLATE/1_dont_ignore.md+0−16
@@ -1,16 +0,0 @@
1---
2name: 'README: DO NOT IGNORE OR DELETE THE ISSUE TEMPLATE'
3about: 'Chose and fill out one of the following templates!'
4title: ''
5labels: priority:ignored-issue-template
6assignees: ''
7
8---
9
10We ask you to not ignore the issue template. Fill it out as good and correct as
11possible. Issues that don't adhere to our request will be closed for ignoring
12the issue template. This is because analyzing a bug without a log file is harder
13than necessary. Low quality bug reports are noise.
14
15Please go back and chose the proper issue template. Opening issues with this
16template will be closed immediately.
.github/ISSUE_TEMPLATE/1_dont_ignore.yml+21−0
@@ -0,0 +1,21 @@
1name: "README: DO NOT IGNORE OR DELETE THE ISSUE TEMPLATE"
2description: "Chose and fill out one of the following templates!"
3labels: ["priority:ignored-issue-template"]
4body:
5- type: markdown
6 attributes:
7 value: >
8 We ask you to not ignore the issue template. Fill it out as good and correct as
9 possible. Issues that don't adhere to our request will be closed for ignoring
10 the issue template. This is because analyzing a bug without a log file is harder
11 than necessary. Low quality bug reports are noise.
12
13
14 Please go back and chose the proper issue template. Opening issues with this
15 template will be closed immediately.
16- type: checkboxes
17 attributes:
18 label: "I ignored the issue template"
19 options:
20 - label: "Ignored the issue template"
21 required: true
.github/ISSUE_TEMPLATE/2_bug_report_linux.md+0−55
@@ -1,55 +0,0 @@
1---
2name: 'Report a Linux Issue'
3about: 'Create a report for a runtime related Linux Issue'
4title: ''
5labels: 'os:linux'
6assignees: ''
7
8---
9
10### Important Information
11
12Provide following Information:
13- mpv version
14- Linux Distribution and Version
15- Source of the mpv binary
16- If known which version of mpv introduced the problem
17- Window Manager and version
18- GPU model, driver and version
19- Possible screenshot or video of visual glitches
20
21If you're not using git master or the latest release, update.
22Releases are listed here: https://github.com/mpv-player/mpv/releases
23
24### Reproduction steps
25
26Try to reproduce your issue with --no-config first. If it isn't reproducible
27with --no-config try to first find out which option or script causes your issue.
28
29If the issue is performance-related, try to reproduce it with --no-config
30--profile=fast, which is designed to work on lower-end mobile devices.
31Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
32
33Describe the reproduction steps as precise as possible. It's very likely that
34the bug you experience wasn't reproduced by the developer because the workflow
35differs from your own.
36
37### Expected behavior
38
39### Actual behavior
40
41### Log file
42
43Make a log file made with -v -v or --log-file=output.txt, attach it to
44the issue, and replace this text with a link to it.
45
46Without the log file, this issue will be closed for ignoring the issue template.
47
48In the case of a crash, please provide a backtrace.
49
50### Sample files
51
52Sample files needed to reproduce this issue can be attached to the issue
53(preferred), or be uploaded to https://0x0.st/ or similar sites.
54(Only needed if the issue cannot be reproduced without it.)
55Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/2_bug_report_linux.yml+77−0
@@ -0,0 +1,77 @@
1name: "Report a Linux Issue"
2description: "Create a report for a runtime related Linux Issue"
3labels: ["os:linux"]
4body:
5- type: textarea
6 attributes:
7 label: "Important Information"
8 description: >
9 - mpv version
10 - Linux Distribution and Version
11 - Source of the mpv binary
12 - If known which version of mpv introduced the problem
13 - Window Manager and version
14 - GPU model, driver and version
15 - Possible screenshot or video of visual glitches
16
17 If you're not using git master or the latest release, update.
18 Releases are listed [here](https://github.com/mpv-player/mpv/releases).
19 value: |-
20 - mpv version:
21 - Linux version:
22 - Source:
23 - Introduced in version:
24 - Window Manager and version:
25 - GPU model, driver and version:
26 validations:
27 required: true
28- type: textarea
29 attributes:
30 label: "Reproduction Steps"
31 description: >
32 Try to reproduce your issue with `--no-config` first. If it isn't reproducible
33 with `--no-config` try to find out which option or script causes your issue.
34
35 If the issue is performance-related, try to reproduce it with `--no-config
36 --profile=fast`, which is designed to work on lower-end mobile devices.
37 Additionally, enable hardware decoding with `--hwdec=yes` or the `Ctrl+h` shortcut.
38
39 Describe the reproduction steps as precise as possible. It's very likely that
40 the bug you experience wasn't reproduced by the developer because the workflow
41 differs from your own.
42 validations:
43 required: true
44- type: textarea
45 attributes:
46 label: "Expected Behavior"
47 placeholder: "What were you expecting?"
48 validations:
49 required: true
50- type: textarea
51 attributes:
52 label: "Actual Behavior"
53 placeholder: "What happened instead?"
54 validations:
55 required: true
56- type: textarea
57 attributes:
58 label: "Log File"
59 placeholder: "Drag and drop log file here (Don't paste content directly)"
60 description: >
61 Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to
62 the issue.
63
64 In the case of a crash, please provide a backtrace.
65
66 Without the log file, this issue will be closed for ignoring the issue template.
67 validations:
68 required: true
69- type: textarea
70 attributes:
71 label: "Sample Files"
72 placeholder: "Drag and drop sample files here"
73 description: >
74 Sample files needed to reproduce this issue can be attached to the issue
75 (preferred), or be uploaded to https://0x0.st/ or similar sites.
76 (Only needed if the issue cannot be reproduced without it.)
77 Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/2_bug_report_macos.md+0−57
@@ -1,57 +0,0 @@
1---
2name: 'Report a macOS Issue'
3about: 'Create a report for a runtime related macOS Issue'
4title: ''
5labels: 'os:mac'
6assignees: ''
7
8---
9
10### Important Information
11
12Provide following Information:
13- mpv version
14- macOS Version
15- Source of the mpv binary or bundle
16- If known which version of mpv introduced the problem
17- Possible screenshot or video of visual glitches
18
19If you're not using git master or the latest release, update.
20Releases are listed here: https://github.com/mpv-player/mpv/releases
21
22### Reproduction steps
23
24Try to reproduce your issue with --no-config first. If it isn't reproducible
25with --no-config try to first find out which option or script causes your issue.
26
27If the issue is performance-related, try to reproduce it with --no-config
28--profile=fast, which is designed to work on lower-end mobile devices.
29Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
30
31Describe the reproduction steps as precise as possible. It's very likely that
32the bug you experience wasn't reproduced by the developer because the workflow
33differs from your own.
34
35### Expected behavior
36
37### Actual behavior
38
39### Log file
40
41Make a log file made with -v -v or --log-file=output.txt, attach it to
42the issue, and replace this text with a link to it.
43
44If you use the Bundle, a default log is created for your last run at
45~/Library/Logs/mpv.log. You can jump to that file via the
46Help > Show log File… menu.
47
48Without the log file, this issue will be closed for ignoring the issue template.
49
50In the case of a crash, please provide the macOS Crash Report (Backtrace).
51
52### Sample files
53
54Sample files needed to reproduce this issue can be attached to the issue
55(preferred), or be uploaded to https://0x0.st/ or similar sites.
56(Only needed if the issue cannot be reproduced without it.)
57Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/2_bug_report_macos.yml+75−0
@@ -0,0 +1,75 @@
1name: "Report a macOS Issue"
2description: "Create a report for a runtime related macOS Issue"
3labels: ["os:mac"]
4body:
5- type: textarea
6 attributes:
7 label: "Important Information"
8 description: >
9 - mpv version
10 - macOS Version
11 - Source of the mpv binary or bundle
12 - If known which version of mpv introduced the problem
13 - Possible screenshot or video of visual glitches
14
15 If you're not using git master or the latest release, update.
16 Releases are listed [here](https://github.com/mpv-player/mpv/releases).
17 value: |-
18 - mpv version:
19 - macOS version:
20 - Source:
21 - Introduced in version:
22 validations:
23 required: true
24- type: textarea
25 attributes:
26 label: "Reproduction Steps"
27 description: >
28 Try to reproduce your issue with `--no-config` first. If it isn't reproducible
29 with `--no-config` try to find out which option or script causes your issue.
30
31 If the issue is performance-related, try to reproduce it with `--no-config
32 --profile=fast`, which is designed to work on lower-end mobile devices.
33 Additionally, enable hardware decoding with `--hwdec=yes` or the `Ctrl+h` shortcut.
34
35 Describe the reproduction steps as precise as possible. It's very likely that
36 the bug you experience wasn't reproduced by the developer because the workflow
37 differs from your own.
38 validations:
39 required: true
40- type: textarea
41 attributes:
42 label: "Expected Behavior"
43 placeholder: "What were you expecting?"
44 validations:
45 required: true
46- type: textarea
47 attributes:
48 label: "Actual Behavior"
49 placeholder: "What happened instead?"
50 validations:
51 required: true
52- type: textarea
53 attributes:
54 label: "Log File"
55 placeholder: "Drag and drop log file here (Don't paste content directly)"
56 description: >
57 Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to
58 the issue. If you use the Bundle, a default log is created for your last run at
59 `~/Library/Logs/mpv.log`. You can jump to that file via the `Help > Show log File…`
60 menu.
61
62 In the case of a crash, please provide the macOS Crash Report (Backtrace).
63
64 Without the log file, this issue will be closed for ignoring the issue template.
65 validations:
66 required: true
67- type: textarea
68 attributes:
69 label: "Sample Files"
70 placeholder: "Drag and drop sample files here"
71 description: >
72 Sample files needed to reproduce this issue can be attached to the issue
73 (preferred), or be uploaded to https://0x0.st/ or similar sites.
74 (Only needed if the issue cannot be reproduced without it.)
75 Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/2_bug_report_windows.md+0−54
@@ -1,54 +0,0 @@
1---
2name: 'Report a Windows Issue'
3about: 'Create a report for a runtime related Windows Issue'
4title: ''
5labels: 'os:win'
6assignees: ''
7
8---
9
10### Important Information
11
12Provide following Information:
13- mpv version
14- Windows Version
15- Source of the mpv binary
16- If known which version of mpv introduced the problem
17- GPU model, driver and version
18- Possible screenshot or video of visual glitches
19
20If you're not using git master or the latest release, update.
21Releases are listed here: https://github.com/mpv-player/mpv/releases
22
23### Reproduction steps
24
25Try to reproduce your issue with --no-config first. If it isn't reproducible
26with --no-config try to first find out which option or script causes your issue.
27
28If the issue is performance-related, try to reproduce it with --no-config
29--profile=fast, which is designed to work on lower-end mobile devices.
30Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
31
32Describe the reproduction steps as precise as possible. It's very likely that
33the bug you experience wasn't reproduced by the developer because the workflow
34differs from your own.
35
36### Expected behavior
37
38### Actual behavior
39
40### Log file
41
42Make a log file made with -v -v or --log-file=output.txt, attach it to
43the issue, and replace this text with a link to it.
44
45Without the log file, this issue will be closed for ignoring the issue template.
46
47In the case of a crash, please provide a backtrace.
48
49### Sample files
50
51Sample files needed to reproduce this issue can be attached to the issue
52(preferred), or be uploaded to https://0x0.st/ or similar sites.
53(Only needed if the issue cannot be reproduced without it.)
54Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/2_bug_report_windows.yml+75−0
@@ -0,0 +1,75 @@
1name: "Report a Windows Issue"
2description: "Create a report for a runtime related Windows Issue"
3labels: ["os:win"]
4body:
5- type: textarea
6 attributes:
7 label: "Important Information"
8 description: >
9 - mpv version
10 - Windows Version
11 - Source of the mpv binary
12 - If known which version of mpv introduced the problem
13 - GPU model, driver and version
14 - Possible screenshot or video of visual glitches
15
16 If you're not using git master or the latest release, update.
17 Releases are listed [here](https://github.com/mpv-player/mpv/releases).
18 value: |-
19 - mpv version:
20 - Windows version:
21 - Source:
22 - Introduced in version:
23 - GPU model, driver and version:
24 validations:
25 required: true
26- type: textarea
27 attributes:
28 label: "Reproduction Steps"
29 description: >
30 Try to reproduce your issue with `--no-config` first. If it isn't reproducible
31 with `--no-config` try to find out which option or script causes your issue.
32
33 If the issue is performance-related, try to reproduce it with `--no-config
34 --profile=fast`, which is designed to work on lower-end mobile devices.
35 Additionally, enable hardware decoding with `--hwdec=yes` or the `Ctrl+h` shortcut.
36
37 Describe the reproduction steps as precise as possible. It's very likely that
38 the bug you experience wasn't reproduced by the developer because the workflow
39 differs from your own.
40 validations:
41 required: true
42- type: textarea
43 attributes:
44 label: "Expected Behavior"
45 placeholder: "What were you expecting?"
46 validations:
47 required: true
48- type: textarea
49 attributes:
50 label: "Actual Behavior"
51 placeholder: "What happened instead?"
52 validations:
53 required: true
54- type: textarea
55 attributes:
56 label: "Log File"
57 placeholder: "Drag and drop log file here (Don't paste content directly)"
58 description: >
59 Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to
60 the issue.
61
62 In the case of a crash, please provide a backtrace.
63
64 Without the log file, this issue will be closed for ignoring the issue template.
65 validations:
66 required: true
67- type: textarea
68 attributes:
69 label: "Sample Files"
70 placeholder: "Drag and drop sample files here"
71 description: >
72 Sample files needed to reproduce this issue can be attached to the issue
73 (preferred), or be uploaded to https://0x0.st/ or similar sites.
74 (Only needed if the issue cannot be reproduced without it.)
75 Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/3_bug_report.md+0−54
@@ -1,54 +0,0 @@
1---
2name: 'Report a different Issue'
3about: 'Create a report for a runtime related Issue'
4title: ''
5labels: ''
6assignees: ''
7
8---
9
10### Important Information
11
12Provide following Information:
13- mpv version
14- Platform and Version
15- Source of the mpv binary
16- If known which version of mpv introduced the problem
17- GPU model, driver and version
18- Possible screenshot or video of visual glitches
19
20If you're not using git master or the latest release, update.
21Releases are listed here: https://github.com/mpv-player/mpv/releases
22
23### Reproduction steps
24
25Try to reproduce your issue with --no-config first. If it isn't reproducible
26with --no-config try to first find out which option or script causes your issue.
27
28If the issue is performance-related, try to reproduce it with --no-config
29--profile=fast, which is designed to work on lower-end mobile devices.
30Additionally, enable hardware decoding with --hwdec=yes or the Ctrl+h shortcut.
31
32Describe the reproduction steps as precise as possible. It's very likely that
33the bug you experience wasn't reproduced by the developer because the workflow
34differs from your own.
35
36### Expected behavior
37
38### Actual behavior
39
40### Log file
41
42Make a log file made with -v -v or --log-file=output.txt, attach it to
43the issue, and replace this text with a link to it.
44
45Without the log file, this issue will be closed for ignoring the issue template.
46
47In the case of a crash, please provide a backtrace.
48
49### Sample files
50
51Sample files needed to reproduce this issue can be attached to the issue
52(preferred), or be uploaded to https://0x0.st/ or similar sites.
53(Only needed if the issue cannot be reproduced without it.)
54Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/3_bug_report.yml+75−0
@@ -0,0 +1,75 @@
1name: "Report a different Issue"
2description: "Create a report for a runtime related Issue"
3labels: []
4body:
5- type: textarea
6 attributes:
7 label: "Important Information"
8 description: >
9 - mpv version
10 - Platform and Version
11 - Source of the mpv binary
12 - If known which version of mpv introduced the problem
13 - GPU model, driver and version
14 - Possible screenshot or video of visual glitches
15
16 If you're not using git master or the latest release, update.
17 Releases are listed [here](https://github.com/mpv-player/mpv/releases).
18 value: |-
19 - mpv version:
20 - Platform version:
21 - Source:
22 - Introduced in version:
23 - GPU model, driver and version:
24 validations:
25 required: true
26- type: textarea
27 attributes:
28 label: "Reproduction Steps"
29 description: >
30 Try to reproduce your issue with `--no-config` first. If it isn't reproducible
31 with `--no-config` try to find out which option or script causes your issue.
32
33 If the issue is performance-related, try to reproduce it with `--no-config
34 --profile=fast`, which is designed to work on lower-end mobile devices.
35 Additionally, enable hardware decoding with `--hwdec=yes` or the `Ctrl+h` shortcut.
36
37 Describe the reproduction steps as precise as possible. It's very likely that
38 the bug you experience wasn't reproduced by the developer because the workflow
39 differs from your own.
40 validations:
41 required: true
42- type: textarea
43 attributes:
44 label: "Expected Behavior"
45 placeholder: "What were you expecting?"
46 validations:
47 required: true
48- type: textarea
49 attributes:
50 label: "Actual Behavior"
51 placeholder: "What happened instead?"
52 validations:
53 required: true
54- type: textarea
55 attributes:
56 label: "Log File"
57 placeholder: "Drag and drop log file here (Don't paste content directly)"
58 description: >
59 Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to
60 the issue.
61
62 In the case of a crash, please provide a backtrace.
63
64 Without the log file, this issue will be closed for ignoring the issue template.
65 validations:
66 required: true
67- type: textarea
68 attributes:
69 label: "Sample Files"
70 placeholder: "Drag and drop sample files here"
71 description: >
72 Sample files needed to reproduce this issue can be attached to the issue
73 (preferred), or be uploaded to https://0x0.st/ or similar sites.
74 (Only needed if the issue cannot be reproduced without it.)
75 Do not use garbage like "cloud storage", especially not Google Drive.
.github/ISSUE_TEMPLATE/4_bug_report_build.md+0−35
@@ -1,35 +0,0 @@
1---
2name: 'Report a build Problem'
3about: 'Create a report for a build related Issue'
4title: ''
5labels: 'core:meson'
6assignees: ''
7
8---
9
10### Important Information
11
12Provide following Information:
13- mpv version
14- Platform and Version
15- meson version
16
17If you're not using git master or the latest release, update.
18Releases are listed here: https://github.com/mpv-player/mpv/releases
19
20### Reproduction steps
21
22Describe the reproduction steps as precise as possible. It's very likely that
23the bug you experience wasn't reproduced by the developer because the workflow
24differs from your own.
25
26### Expected behavior
27
28### Actual behavior
29
30### Log file
31
32Attach meson-logs/meson-log.txt or meson setup build output to the issue,
33and replace this text with a link to it.
34
35Without the log file, this issue will be closed for ignoring the issue template.
.github/ISSUE_TEMPLATE/4_bug_report_build.yml+51−0
@@ -0,0 +1,51 @@
1name: "Report a build Problem"
2description: "Create a report for a build related Issue"
3labels: ["core:meson"]
4body:
5- type: textarea
6 attributes:
7 label: "Important Information"
8 description: >
9 - mpv version
10 - Platform and Version
11 - Meson version
12
13 If you're not using git master or the latest release, update.
14 Releases are listed [here](https://github.com/mpv-player/mpv/releases).
15 value: |-
16 - mpv version:
17 - Platform version:
18 - Meson version:
19 validations:
20 required: true
21- type: textarea
22 attributes:
23 label: "Reproduction Steps"
24 description: >
25 Describe the reproduction steps as precise as possible. It's very likely that
26 the bug you experience wasn't reproduced by the developer because the workflow
27 differs from your own.
28 validations:
29 required: true
30- type: textarea
31 attributes:
32 label: "Expected Behavior"
33 placeholder: "What were you expecting?"
34 validations:
35 required: true
36- type: textarea
37 attributes:
38 label: "Actual Behavior"
39 placeholder: "What happened instead?"
40 validations:
41 required: true
42- type: textarea
43 attributes:
44 label: "Log File"
45 placeholder: "Drag and drop log file here (Don't paste content directly)"
46 description: >
47 Attach meson-logs/meson-log.txt or meson setup build output to the issue.
48
49 Without the log file, this issue will be closed for ignoring the issue template.
50 validations:
51 required: true
.github/ISSUE_TEMPLATE/5_feature_request.md+0−21
@@ -1,21 +0,0 @@
1---
2name: 'Request a new Feature'
3about: 'Create a request for a new feature'
4title: ''
5labels: 'meta:feature-request'
6assignees: ''
7
8---
9
10Before requesting a new feature make sure it hasn't been requested yet.
11https://github.com/mpv-player/mpv/labels/meta%3Afeature-request
12
13### Expected behavior of the wanted feature
14
15### Alternative behavior of the wanted feature
16
17### Log file
18
19Even if you think it's not necessary at first, it might help us later to find
20possible issues. Make a log file made with -v -v or --log-file=output.txt,
21attach it to the issue, and replace this text with a link to it.
.github/ISSUE_TEMPLATE/5_feature_request.yml+22−0
@@ -0,0 +1,22 @@
1name: "Request a new Feature"
2description: "Create a request for a new feature"
3labels: ["meta:feature-request"]
4body:
5- type: textarea
6 attributes:
7 label: "Expected behavior of the wanted feature"
8 description: >
9 Before requesting a new feature make sure it hasn't been
10 [requested yet](https://github.com/mpv-player/mpv/labels/meta%3Afeature-request).
11 validations:
12 required: true
13- type: textarea
14 attributes:
15 label: "Alternative behavior of the wanted feature"
16- type: textarea
17 attributes:
18 label: "Log File"
19 description: >
20 Even if you think it's not necessary at first, it might help us later to find
21 possible issues. Make a log file made with `-v -v` or `--log-file=output.txt` and
22 attach it to the issue.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t