summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEd Tanous <edtanous@google.com>2021-08-13 21:16:58 +0300
committerGunnar Mills <gmills@us.ibm.com>2021-08-17 19:02:41 +0300
commitffb05364bbd72df89f3b3c558cdbee887681387b (patch)
tree50e485b94320eaa2fbc723f0e5ff7df2ef6f267f
parentd699cf969aea5a059b95151f58e054c928f076cc (diff)
downloadbmcweb-ffb05364bbd72df89f3b3c558cdbee887681387b.tar.xz
Add details to bug template
A large number of bugs get filed against OpenBMC forks, and platforms that are not upstream. Change the wording on the bug template to make clear the fields should be expected to be from upstream, and explicitly call out if qemu builds are being used, to help in maintainers reproducing. Tested: N/A, documentation change. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: Ibff2dcbfb1755fb14d21621ebd0cf86e1d3ab2fc
-rw-r--r--.github/ISSUE_TEMPLATE/bug_report.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 2dd250cb65..22c4a69fe8 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -11,8 +11,10 @@ assignees: ''
A clear and concise description of what the bug is.
**Environment**
-What OpenBMC platform was this found on?
-What specific OpenBMC versions did you use?
+What OpenBMC platform was this found on? If this was tested in QEMU, please add
+
+What specific OpenBMC versions (SHA1) did you use?
+(note, SHA1 should be resolvable to https://github.com/openbmc/openbmc)
**To Reproduce**
Steps to reproduce the behavior: