From 31d48510899099a0d8a76a27040cb7285be4b0a0 Mon Sep 17 00:00:00 2001 From: Jose Diaz-Gonzalez Date: Sat, 19 May 2018 03:03:59 -0400 Subject: [PATCH] docs: clarify why dokku report information is useful Also note that it can be run without any arguments. Refs #3192 --- ISSUE_TEMPLATE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md index f79a3207a..5de39d2a5 100644 --- a/ISSUE_TEMPLATE.md +++ b/ISSUE_TEMPLATE.md @@ -6,6 +6,8 @@ Description of problem: Output of the following commands - `dokku report APP_NAME` + - For problems affecting all applications, the report output for a broken application is useful for our debugging. + - You may also run `dokku report` without any arguments to display the top-level reporting information. - `docker inspect CONTAINER_ID` (if applicable): (BEWARE: `docker inspect` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX): - `cat /home/dokku//nginx.conf` (if applicable):