RepoMirrors
/
mpv
mirror of https://github.com/mpv-player/mpv
1
0
Fork 0
Code Issues Releases Wiki Activity

github/issue_template: reword log file instructions

This commit is contained in:
der richter 2024-04-21 22:45:06 +02:00
parent 704863a016
commit 9f2590b6d1
5 changed files with 39 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.github/ISSUE_TEMPLATE/2_bug_report_linux.yml vendored
View File

@ -63,11 +63,17 @@ body:
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.
Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and 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

13
.github/ISSUE_TEMPLATE/2_bug_report_macos.yml vendored
View File

@ -59,13 +59,18 @@ body:
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.
Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
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.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and attach it to the issue.
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

10
.github/ISSUE_TEMPLATE/2_bug_report_windows.yml vendored
View File

@ -61,11 +61,17 @@ body:
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.
Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and 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

10
.github/ISSUE_TEMPLATE/3_bug_report.yml vendored
View File

@ -61,11 +61,17 @@ body:
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.
Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and 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

8
.github/ISSUE_TEMPLATE/5_feature_request.yml vendored
View File

@ -18,5 +18,9 @@ body:
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.
possible issues. Make a log file with `--log-file=output.txt`, which is our preferred way,
and attach it to the issue.
If you have trouble producing a log file, you can alternatively use `-v -v`, save the
terminal output to a file, and attach it to the issue.