From 5b9761cbae177740f3f4cf5060ef7be56b54dd1d Mon Sep 17 00:00:00 2001 From: nick n <39005454+inphobia@users.noreply.github.com> Date: Fri, 19 Jul 2019 01:14:27 +0200 Subject: [PATCH] netdisco-docker triage point netdisco docker users to the docker issue tracker as a first step, so we can spent less time on triaging issues. netdisco docker has some quirks not present in regular netdisco, if it turns out to be non container related we can always move the issue back to this tracker. btw, seems we need to change our issue templates, but only project admins can do so: "You are using an old version of issue templates. Please update to the new issue template workflow. Learn more." -> https://help.github.com/articles/about-issue-and-pull-request-templates --- .github/issue_template.md | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/.github/issue_template.md b/.github/issue_template.md index 386b0639..94bdb323 100644 --- a/.github/issue_template.md +++ b/.github/issue_template.md @@ -1,17 +1,23 @@ - + - +STOP! If your ticket is about a device not being detected correctly, +see SNMP::Info: https://github.com/netdisco/snmp-info/issues/new - - +STOP! If you have new MIBs to submit, +see netdisco-mibs: https://github.com/netdisco/netdisco-mibs/issues/new - +STOP! If you are running a netdisco docker setup, +see netdisco-docker: https://github.com/netdisco/netdisco-docker/issues/new + +everything else about Netdisco's behaviour is good, here :-D + +when including netdisco config snippets, whitespace matters since it's a yaml file +for github issues it really helps if you include the relevant config parts in a codeblock (code fencing) +see the "code" subject on https://guides.github.com/features/mastering-markdown/ for that) +this should preserve spaces in the issue tracker and make troubleshooting quicker +--> - - - - ## Expected Behavior