From 05f018b81aa3aec27dc61cbc7308b91cc858dfd8 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 9 Nov 2019 23:50:32 +0100 Subject: github: suggest using as github attachment for log files It's not that we _want_ the log to be on an external site. We just want the log, somehow. Probably not pasted inline into the issue text. Also reword the "we are assholes who really want logs" part of the text. It's a subtle balance between trying to be nice and being a complete asshole, but no matter what you do, it will always sound like the latter, so be direct. --- .github/ISSUE_TEMPLATE | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE b/.github/ISSUE_TEMPLATE index 895f79f62f..6690a0c739 100644 --- a/.github/ISSUE_TEMPLATE +++ b/.github/ISSUE_TEMPLATE @@ -12,12 +12,12 @@ Releases are listed here: https://github.com/mpv-player/mpv/releases ### Log file Make a log file made with -v -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. +https://0x0.st/ or attach it the github issue, 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. +If this is a normal runtime bug, and no log is provided, the issue 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. ### Sample files -- cgit v1.2.3