From 829a6b7aef714efbcc2ba6ae76e2a508ef7d0597 Mon Sep 17 00:00:00 2001 From: Karl-Philipp Richter Date: Sun, 15 Dec 2019 12:15:52 +0100 Subject: [PATCH] Use details tag around code backticks for 'helm get' output in issue template The output can be quite long and long output clutters up the issue description. Note that the empty line is necessary in order for the code to be parsed correctly (see https://github.com/dear-github/dear-github/issues/166#issuecomment-322367328 for details). --- .github/ISSUE_TEMPLATE/bug_report.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index f57c28413..61de9e089 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -20,9 +20,14 @@ e.g. `helm get elasticsearch` (replace `elasticsearch` with the name of your hel *If you find some secrets in plain text in `helm get release` output you should use [Kubernetes Secrets](https://kubernetes.io/docs/concepts/configuration/secret/) to managed them is a secure way (see [Security Example](https://github.com/elastic/helm-charts/blob/master/elasticsearch/examples/security/security.yml#L23-L38)).* +
+Output of helm get release + ``` ``` +
+ **Describe the bug:** **Steps to reproduce:**